per cu .

~~~

While using Smallrye Reactive Messaging (RabbitMQ), I encountered a problem when restarting quarkus:dev with 's' (Force restart). The result is each time the restart occurs, previous TCP connections created for consumer channels remain open and begin to build up. It's important to note that I am not leveraging the Dev Services for RabbitMQ and instead manually running a local container instance of RabbitMQ. No exceptions are actually thrown during the force restart, however when a the consumer is attempting to receive a message from a queue while duplicate TCP connections are created for the same channel, the consumer fails to successfully consume the message.

Expected behavior
Restarting quarkus dev mode using the live-reload feature should not cause old TCP connections to remain and build up.

~~~