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
0.11 AMQP/Rabbit reconnect issue #1162
Comments
Does jasmin retry connection when rabbit goes down ? |
Hi, No jasmin restart is required. It receives messages via smpp, publishes to rabbit but it does not consume until restart. |
Do you have any idea of why the consumer stopped in jasmin ? |
Hi,
and will not consume new messages until restart. |
Can confirm, I am seeing that as well. Jasmin will not reconnect unless restarted. Happens pretty frequently, I have tried to use various versions of RabbitMQ, it does not help. The amqp client log is pretty the same a for OP:
|
Also to add to OP: RabbitMQ does not go down itself, it just closes that specific connection and expects Jasmin to reconnect. |
Same happens to me once a day, any ideas?
|
i think you are setting the heartbeat = 1 is not good. any latency and rabbitmq will consider the connection dead. rabbitmq can see this setting and expect the heartbeat. if there is any delay for whatever reason, your connection is considered dead from rabbit side.
i do a check on the |
Hi all. We are having the same issue (Jasmin does not try to reconnect after a disconnection from Rabbit). We observed this yesterday when Rabbit restarted for maintenance). |
Hi all, I am also having the same issue, any idea how to solve it? |
I think it's issue that is very long in a design. Seems that after disconnect from AMQ Jasmin cannot recover
Rabbit and jasmin are on localhost on docker env with following setting:
Jasmin 0.11.0 official docker image, rabbitmq:3-management-alpine
rabbit stacktrace:
The text was updated successfully, but these errors were encountered: