Julien Viet
Julien Viet
a PR would be appreciated, this subject actually becomes more important with the advent of virtual threads and shadow context (in vertx 5)
@Onkelborg you should read the contribution guide and that is enough
Looking at this issue, I am doing some tests and I can see that when the verticle is undeployed, the message consumer is always unregistered before the assigned executor pool...
so it seems that the event bus consumer is not unregistered ? when the verticle is undeployed we have the following sequence: 1. the context close future is closed which...
Overall I think when a synchronous uncaught exception is thrown (like the rejection) this should be handled appropriately by the event-bus 1. in case of publish it should be logged...
FTR here is a reproducer: ```java @Test public void testSome() { ThreadLocal reject = new ThreadLocal(); Vertx vertx = new VertxBuilder() .executorServiceFactory(new ExecutorServiceFactory() { @Override public ExecutorService createExecutor(ThreadFactory threadFactory, Integer...
This reproducer uses a trick since I am not able to reproduce the consumer/worker inverted sequence.
request (send with a response)
@lucamolteni we support JDBC based implementations with https://github.com/vert-x3/vertx-jdbc-client
did you check https://repo1.maven.org/maven2/io/vertx/vertx-core/4.5.10/vertx-core-4.5.10-native-image.jar ?