-
Notifications
You must be signed in to change notification settings - Fork 196
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
Issue recreating connection to a queue after a connection problem #632
Comments
This could be a duplicate of #594. How certain are you that there is a strong reference chain to the Channel or Queue? |
Also confirmed that 9.4.1 does not reconnect after a rabbit restart but 8.2.1 does. In my testing, the application gets blocked on this line waiting for the |
@drsnyder did you try to upgrade to the latest release? |
Yes, I tried upgrading. Release 9.4.2 also does not work. |
Current version is https://pypi.org/project/aio-pika/9.5.4/ |
@mosquito, thanks for getting back to me so fast. Sorry, 9.5.4 doesn't work either. It appears to be reconnecting but the consumer call backs are not receiving messages. Similar to the OP, I get:
|
Hi my application is using aio-pika=9.4.1 to connect to a rabbitmq. I'm testing under docker environment and if I manually shutdown rabbit I see following log messages:
but when rabbit restarts I see following errors:
then the application is successfully connecting to new instance (no more error where logged) but it's not true for the exchange and queue (there is no consumer).
The application is now blocked whiting for new messages that never be read.
Using aio-pika==8.2.1 the application were working fine, I got similar error when the rabbitmq is down, but when it comes up again even the consumer is connected and messages are processed correctly.
The text was updated successfully, but these errors were encountered: