-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dev mode reload - rabbitmq - multiple rabbitmq connections #39433
Comments
/cc @cescoffier (reactive-messaging), @ozangunalp (reactive-messaging) |
Which version of Quarkus are you using? I fixed an issue related to that recently. |
3.8.2 |
Could you provide a standalone minimal reproducer? |
Reproduction would need an existing rabbitmq server, as using devservices would affect the problem itself (I think, I can't get docker to work on my machine because of company policy)... so the reproducer would just be an app with a connection to rabbitmq server. I created a simple one - https://github.com/rastislavpapp/quarkus-39433-bug-reproducer The issue happens every time I restart (via dev mode). |
Describe the bug
I'm consuming from a rabbitmq queue in my quarkus app. When reloading the app in dev mode, I'm expecting that the app will disconnect from RabbitMQ, and then connect again. This is what happens, but after the reload, there is 2 connections to the queue instead of 1. I think it's because when disconnecting, a shutdown handler of a queue consumer is triggered (see
io.vertx.rabbitmq.impl.RabbitMQClientImpl#basicConsumer
), which reconnects back. And then the app reloads and connects again.Expected behavior
after dev mode reload, there should be only 1 connection to consumed queue
Actual behavior
after dev mode reload, there are multiple connections to consumed queue
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: