[rabbitmq-discuss] Orphaned channels after connection close in Rabbit 3.1.4
matthias at rabbitmq.com
Thu Aug 15 10:54:15 BST 2013
On 15/08/13 10:50, Paul Bowsher wrote:
> Thanks for the reply. When you say resource alarms, do you mean on the
> server or from the clients?
> It seems that we have a sick rabbit on node A. How can we
> help diagnose this?
Check the logs and the management UI. For connections to be in the
'blocked' state for any significant duration of time, there must be a
triggering memory and/or disk alarm. Which should be very obvious in the
logs and UI.
More information about the rabbitmq-discuss