During development redeploy time is critical, so it would be nice to eliminate as much as possible. In my Jakarta EE 10 .war project I connected 10 channels to Kafka topics via microprofile reactive streams. I bring up Kafka via Docker before and deploy the .war to Wildfly 28.0.1 which use smallrye-reactive-messaging. The channels are connected after the deployment is finished and this takes only a short amount of time.

But on undeployment the channels are closed synchronously one by one and the overall time is up to 10 seconds. I checked out if it is possible to reduce this time, by defining a shorter timeout or something else. But I did not find anything what can be configured here.

So my question would be if it is possible to add the smallrye-in-memory connector to Wildfly and use it during development? This would also reduce the dependency to a running Kafka during development.

This question is copied from Stackoverflow . I gave already an answer to my own question on Stackoverflow. So I put the smallrye-in-memory connector as a module to wildfly but it is a little bit hackish.

It would be nice to have it out of the box included