[rabbitmq-discuss] Memory limit cleanup, hanging connections.

Mon Oct 15 10:49:51 BST 2012

Hi,

We ran into a situation where we hit a memory limit by queues being filled
upt, causing all connections to be in a blocked or blocking state.

We're killed all connections from the client side and deleted the filled up
queues.
While the broker is still cleaning up /msg_store_transient (which is
horribly slow), it also still lists all the connections as alive, being
still blocked.

Is it possible that when the broker is still in memory alarm mode, the
connections (blocked) are not checked for their heartbeat and therefore are
kept alive?

And what is the cause of the slowness of the cleanup when deleting queues
with only transient messages?

- Irmo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121015/0db0b661/attachment.htm>