Replies: 1 comment 1 reply
-
This is just log noise. A channel does not get a delivery ack (possibly because the queue processes were already stopped) and that makes it time out on its own shutdown, which one of the closing connections logs. Shutdown order in environments with a lot of parallelism can result in scenarios like this: queues shut down before things that depend on them. It should not cause any harm as long as clients use publisher confirms and consumer acknowledgments. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I am facing this issue with rabbitmq and the log is below. Before the start of the log, there is no log at all for 2 days. This is a DR env and hasn't seen any activity since May 6th. I've seen discussions where below error will be shown when rabbitmq connection is closed but that's not the case this time. The rabbitmq connections were not closed.
Is it possible to find out what caused the shutdown using the log below?
Rabbitmq ver: 3.11.7
Erlang 25.2.1
Beta Was this translation helpful? Give feedback.
All reactions