the service doesn't start outside of docker #1785

engineer-plus-plus · 2023-06-27T11:53:49Z

engineer-plus-plus
Jun 27, 2023

Having started RMQ in docker but not svc-xample-j, as shown below, I attempt to start the service using gradle bootRun command. The service never completes initialization. It gets stuck at 90% forever.

"But, Ilya, why is this an issue, why not just run in docker?" Because it's much easier to develop service when it's not isolated by a powerful indirection such as Docker. And it just should run locally, IMHO.

 ilya_standard@ilyaAgile6Mac  ~/Theta/abd-vro/domain-xample/svc-xample-j   develop ±  docker ps
CONTAINER ID   IMAGE                                COMMAND                  CREATED        STATUS                  PORTS                                                                                                         NAMES
fc8a754058d4   va/abd_vro-xample-workflows:latest   "/app/entrypoint-wra…"   12 hours ago   Up 12 hours (healthy)                                                                                                                 vro-xample-workflows-1
170bedadb9dc   redis                                "docker-entrypoint.s…"   12 hours ago   Up 12 hours             0.0.0.0:6379->6379/tcp                                                                                        vro-redis-service-1
f16fa65ac85e   rabbitmq:3-management                "docker-entrypoint.s…"   12 hours ago   Up 12 hours (healthy)   4369/tcp, 5671/tcp, 0.0.0.0:5672->5672/tcp, 15671/tcp, 15691-15692/tcp, 25672/tcp, 0.0.0.0:15672->15672/tcp   vro-rabbitmq-service-1
8eebf9f18c44   va/abd_vro-postgres                  "/our-entrypoint.sh"     12 hours ago   Up 12 hours (healthy)   0.0.0.0:5432->5432/tcp                                                                                        vro-postgres-service-1
 ilya_standard@ilyaAgile6Mac  ~/Theta/abd-vro/domain-xample/svc-xample-j   develop ±  gradle bootRun
executing gradlew instead of gradle

> Task :domain-xample:svc-xample-j:bootRun

  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::               (v2.7.12)

2023-06-27 05:48:12.074  INFO 8706 --- [           main] g.v.v.s.x.JavaMicroserviceApplication    : Starting JavaMicroserviceApplication using Java 17.0.7 on ilyaAgile6Mac with PID 8706 (/Users/ilya_standard/Theta/abd-vro/domain-xample/svc-xample-j/build/classes/java/main started by ilya_standard in /Users/ilya_standard/Theta/abd-vro/domain-xample/svc-xample-j)
2023-06-27 05:48:12.076  INFO 8706 --- [           main] g.v.v.s.x.JavaMicroserviceApplication    : No active profile set, falling back to 1 default profile: "default"
2023-06-27 05:48:12.557  INFO 8706 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 8080 (http)
2023-06-27 05:48:12.562  INFO 8706 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
2023-06-27 05:48:12.562  INFO 8706 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.75]
2023-06-27 05:48:12.608  INFO 8706 --- [           main] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
2023-06-27 05:48:12.608  INFO 8706 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 510 ms
2023-06-27 05:48:12.987  INFO 8706 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 8080 (http) with context path ''
2023-06-27 05:48:13.016  INFO 8706 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 10011 (http)
2023-06-27 05:48:13.016  INFO 8706 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
2023-06-27 05:48:13.016  INFO 8706 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.75]
2023-06-27 05:48:13.021  INFO 8706 --- [           main] o.a.c.c.C.[Tomcat-1].[localhost].[/]     : Initializing Spring embedded WebApplicationContext
2023-06-27 05:48:13.022  INFO 8706 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 33 ms
2023-06-27 05:48:13.027  INFO 8706 --- [           main] o.s.b.a.e.web.EndpointLinksResolver      : Exposing 1 endpoint(s) beneath base path '/actuator'
2023-06-27 05:48:13.043  INFO 8706 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 10011 (http) with context path ''
2023-06-27 05:48:13.045  INFO 8706 --- [           main] o.s.a.r.c.CachingConnectionFactory       : Attempting to connect to: [localhost:5672]
2023-06-27 05:48:13.077  INFO 8706 --- [           main] o.s.a.r.c.CachingConnectionFactory       : Created new connection: rabbitConnectionFactory#553da911:0/SimpleConnection@7a31ca20 [delegate=amqp://[email protected]:5672/, localPort= 60739]
2023-06-27 05:48:13.080  INFO 8706 --- [           main] o.s.amqp.rabbit.core.RabbitAdmin         : Auto-declaring a non-durable or auto-delete Exchange (xample) durable:true, auto-delete:true. It will be deleted by the broker if it shuts down, and can be redeclared by closing and reopening the connection.
2023-06-27 05:48:13.080  INFO 8706 --- [           main] o.s.amqp.rabbit.core.RabbitAdmin         : Auto-declaring a non-durable, auto-delete, or exclusive Queue (serviceJ) durable:true, auto-delete:true, exclusive:false. It will be redeclared if the broker stops and is restarted while the connection factory is alive, but all messages will be lost.
2023-06-27 05:48:13.127  INFO 8706 --- [           main] g.v.v.s.x.JavaMicroserviceApplication    : Started JavaMicroserviceApplication in 1.245 seconds (JVM running for 1.375)
<===========--> 90% EXECUTING [5m 47s]
> :domain-xample:svc-xample-j:boot

yoomlam · 2023-06-27T15:29:19Z

yoomlam
Jun 27, 2023

To run any VRO component outside of Docker, you'll need to configure your environment so that the component can communicate with containers inside of Docker. Luke documented some steps for running vro-app in IntelliJ.

For the svc-xample-j microservice, no additional setup is necessary since the defaults to connect to the MQ should work. This worked for me:

source scripts/setenv.sh
./gradlew :dockerComposeUp
./gradlew :domain-xample:dockerComposeUp
COMPOSE_PROFILES="" ./gradlew :app:dockerComposeUp

# Stop the Docker instance of svc-xample-j so you can run svc-xample-j's bootRun outside of Docker
❯ docker stop vro-svc-xample-j-1

❯ ./gradlew :domain-xample:svc-xample-j:bootRun
> Task :domain-xample:svc-xample-j:bootRun

  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::               (v2.7.12)

2023-06-27 10:20:59.356  INFO 52541 --- [           main] g.v.v.s.x.JavaMicroserviceApplication    : Starting JavaMicroserviceApplication using Java 17.0.3 on YoomsMBP.lams with PID 52541 (/Users/yoom/dev/abd-vro/domain-xample/svc-xample-j/build/classes/java/main started by yoom in /Users/yoom/dev/abd-vro/domain-xample/svc-xample-j)
2023-06-27 10:20:59.357  INFO 52541 --- [           main] g.v.v.s.x.JavaMicroserviceApplication    : No active profile set, falling back to 1 default profile: "default"
2023-06-27 10:20:59.745  INFO 52541 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 8080 (http)
2023-06-27 10:20:59.750  INFO 52541 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
2023-06-27 10:20:59.750  INFO 52541 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.75]
2023-06-27 10:20:59.788  INFO 52541 --- [           main] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
2023-06-27 10:20:59.788  INFO 52541 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 413 ms
2023-06-27 10:21:00.089  INFO 52541 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 8080 (http) with context path ''
2023-06-27 10:21:00.110  INFO 52541 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 10011 (http)
2023-06-27 10:21:00.110  INFO 52541 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
2023-06-27 10:21:00.110  INFO 52541 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.75]
2023-06-27 10:21:00.115  INFO 52541 --- [           main] o.a.c.c.C.[Tomcat-1].[localhost].[/]     : Initializing Spring embedded WebApplicationContext
2023-06-27 10:21:00.115  INFO 52541 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 25 ms
2023-06-27 10:21:00.119  INFO 52541 --- [           main] o.s.b.a.e.web.EndpointLinksResolver      : Exposing 1 endpoint(s) beneath base path '/actuator'
2023-06-27 10:21:00.135  INFO 52541 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 10011 (http) with context path ''
2023-06-27 10:21:00.136  INFO 52541 --- [           main] o.s.a.r.c.CachingConnectionFactory       : Attempting to connect to: [localhost:5672]
2023-06-27 10:21:00.173  INFO 52541 --- [           main] o.s.a.r.c.CachingConnectionFactory       : Created new connection: rabbitConnectionFactory#10f477e2:0/SimpleConnection@53feeac9 [delegate=amqp://[email protected]:5672/, localPort= 51657]
2023-06-27 10:21:00.175  INFO 52541 --- [           main] o.s.amqp.rabbit.core.RabbitAdmin         : Auto-declaring a non-durable or auto-delete Exchange (xample) durable:true, auto-delete:true. It will be deleted by the broker if it shuts down, and can be redeclared by closing and reopening the connection.
2023-06-27 10:21:00.175  INFO 52541 --- [           main] o.s.amqp.rabbit.core.RabbitAdmin         : Auto-declaring a non-durable, auto-delete, or exclusive Queue (serviceJ) durable:true, auto-delete:true, exclusive:false. It will be redeclared if the broker stops and is restarted while the connection factory is alive, but all messages will be lost.
2023-06-27 10:21:00.205  INFO 52541 --- [           main] g.v.v.s.x.JavaMicroserviceApplication    : Started JavaMicroserviceApplication in 1.003 seconds (JVM running for 1.146)

In a new console, run:

❯ curl -X POST "http://localhost:8110/v3/xample-resource" -H "accept: application/json" -H "Content-Type: application/json" -d '{"resourceId":"12343","diagnosticCode":"J"}'
{"resourceId":"12343","diagnosticCode":"J","status":"PROCESSING","statusCode":0}%

As a result, you should see the following appended to the svc-xample-j log in the first console:

2023-06-27 10:23:16.239  INFO 52541 --- [ntContainer#0-1] g.v.v.s.xample.XampleJavaMicroservice    : Received: SomeDtoModel(resourceId=12343, diagnosticCode=J, status=PROCESSING, statusCode=0, statusMessage=null)
<===========--> 90% EXECUTING [4m 17s]
> :domain-xample:svc-xample-j:bootRun

0 replies

dfitchett · 2023-06-27T17:52:31Z

dfitchett
Jun 27, 2023
Maintainer

I am able to replicate @yoomlam steps, with the addition of running ./gradlew clean build docker before
source scripts/setenv.sh
./gradlew :dockerComposeUp
./gradlew :domain-xample:dockerComposeUp
COMPOSE_PROFILES="" ./gradlew :app:dockerComposeUp

0 replies

engineer-plus-plus · 2023-06-28T00:46:11Z

engineer-plus-plus
Jun 28, 2023
Author

So for @yoomlam the gradle build also hangs at 90%. But the service seems to work. It responds to messages sent to it. That's all I really care about for now.

But this is ugly that the build doesn't confirm success. That means that the service, while appears ok, is in unknown state. This can lead to maintainability nightmare where somebody spends long time looking for bug in his code while the bad behavior is due to the incorrect initialization.

Have you tried running it with --debug flag. The output is interesting,

0 replies

dianagriffin · 2023-06-28T23:09:28Z

dianagriffin
Jun 28, 2023

@engineer-plus-plus @yoomlam

But the service seems to work. It responds to messages sent to it. That's all I really care about for now.

I'm interpreting this to mean that this particular issue can be closed as resolved. Is that correct?

But this is ugly that the build doesn't confirm success. That means that the service, while appears ok, is in unknown state. This can lead to maintainability nightmare where somebody spends long time looking for bug in his code while the bad behavior is due to the incorrect initialization.

Does this suggest that a new ticket needs to be created with the goal of having the build confirm success?

0 replies

yoomlam · 2023-06-29T15:01:32Z

yoomlam
Jun 29, 2023

@engineer-plus-plus @yoomlam

But the service seems to work. It responds to messages sent to it. That's all I really care about for now.

I'm interpreting this to mean that this particular issue can be closed as resolved. Is that correct?

That was a misinterpretation of the Gradle output. It's not hanging and is working as expected.

But this is ugly that the build doesn't confirm success. That means that the service, while appears ok, is in unknown state. This can lead to maintainability nightmare where somebody spends long time looking for bug in his code while the bad behavior is due to the incorrect initialization.

Does this suggest that a new ticket needs to be created with the goal of having the build confirm success?

No. Again, it was a misinterpretation of the Gradle output and unfamiliarity with the bootRun Gradle task.

0 replies

engineer-plus-plus · 2023-07-10T01:23:09Z

engineer-plus-plus
Jul 10, 2023
Author

I took the liberty to convert the issue to discussion. Which it was intended to be to begin with. I hope it's ok.

The resolution was following: @yoomlam was right -- I was just confused by gradle output.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

the service doesn't start outside of docker #1785

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 6 comments

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

Select a reply

the service doesn't start outside of docker #1785

engineer-plus-plus Jun 27, 2023

Replies: 6 comments

yoomlam Jun 27, 2023

dfitchett Jun 27, 2023 Maintainer

engineer-plus-plus Jun 28, 2023 Author

dianagriffin Jun 28, 2023

yoomlam Jun 29, 2023

engineer-plus-plus Jul 10, 2023 Author

engineer-plus-plus
Jun 27, 2023

yoomlam
Jun 27, 2023

dfitchett
Jun 27, 2023
Maintainer

engineer-plus-plus
Jun 28, 2023
Author

dianagriffin
Jun 28, 2023

yoomlam
Jun 29, 2023

engineer-plus-plus
Jul 10, 2023
Author