<br><br><div class="gmail_quote">On Mon, Oct 15, 2012 at 12:44 PM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">Yes, that's absolutely correct. The blocked connections don't perform any network operations at all - which means that not only don't they check for heartbeats, they don't even detect the TCP connection being torn down. As soon as the memory alarm clears, the connections will unblock, notice the TCP connection having gone away, and vanish.</div>
<div class="im"><br></div></blockquote><div><br></div><div>Ok, good to know. I reckon the connections themselves don't take that much resources or keep hold of memory consuming parts? That it's purely the queues and their messages eating the memory?</div>
<div>�</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If you've "filled up" all your queues then they will have been paging to disc for some time - cleaning all that up can be quite slow.<br>
<br></blockquote><div><br></div><div>Any reason why this is that slow? Does it look up every message 1 by 1 in the storage or something?</div><div>�</div><div>Cheers,</div><div>- Irmo</div></div>