You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not really sure where the problem may be, you can find the connection code below.
All I'm doing is running the program, seeing it connect in RabbitMQ's Management, leave it for 5 minutes then close the program and the connection still shows in Management.
I think this also relates to an issue I'm having where in Management it looks like the message is being handled but does not ack after a long wait.
I am also experiencing similar issue. After 5 mins of inactivity (not receiving messages) my application doesn't receive any subsequent messages, even though the rabbitmq management UI shows as connected, and receiving messages.
I think this may be due the client not having heartbeats. (https://www.rabbitmq.com/heartbeats.html) Depending of what version of rabbitmq server running, the default could be set to 580, and the interval heartbeats is set to 580/2 or 290 secs which is 4.8mins. After 2 failed heartbeats the connection is dropped.
I am also experiencing similar issue. After 5 mins of inactivity (not receiving messages) my application doesn't receive any subsequent messages, even though the rabbitmq management UI shows as connected, and receiving messages.
Not really sure where the problem may be, you can find the connection code below.
All I'm doing is running the program, seeing it connect in RabbitMQ's Management, leave it for 5 minutes then close the program and the connection still shows in Management.
I think this also relates to an issue I'm having where in Management it looks like the message is being handled but does not ack after a long wait.
The text was updated successfully, but these errors were encountered: