JVM stops right after deploying virtual verticle

[tsegismont]

JVM stops right after deploying virtual verticle

[vietj]

I believe we should start to provide different examples when the code is started from a non vertx thread, e.g.

vertx.deployVerticle(...).await();

would make sense to me

• it forces the main thread to await the success or failure of the deployment
• it will allow event-loop to be started and prevent the exit

However await() currently is only supported on worker threads, but it would make sense to support it from a non vertx event-loop thread.

[tsegismont]

Quick analysis: when the virtual thread model is used, no event loop is created before the http server is started. Vert.x threads are non-daemon by default, and they prevent the JVM from shutting down.

In the sample before, the application reaches the end of the main method before the virtual thread triggers the creation of the http server.

That is why the JVM shut downs early.

[tsegismont]

cc @vietj

Many applications rely on the fact that the JVM will stay alive even after the main thread reaches the end of the method.

[vietj]

yeah I found this issue too a while ago, I don't know yet what is the best way to address it.

I believe that applications should not rely on vertx though

[tsegismont]

I just found that this (funny?) behavior:

vertx.deployVerticle(new MainVerticle(), deploymentOptions)

to:

vertx.deployVerticle(MainVerticle.class.getName(), deploymentOptions)

Then the JVM doesn't stop because Vert.x starts an event loop

I believe that applications should not rely on vertx though

I understand. On the other hand, we have so many examples which look like the example in the description.

[tsegismont]

Perhaps we can find the difference between deploying a verticle with a class name or with a class or an instance, and make sure it always works like deploying using a class name.