<div>Thank you for your reply!</div><div><br></div><div>This might be a little question but, if RabbitMQ runs out of memory, and I am unable to open a new channel, how would one then consume off the queue, if one isn't able to open a channel to do so? Or is this something which has been solved with the new persister?</div>
<div><br></div><div>Cheers</div><div><br>Cal</div><div><br><div class="gmail_quote">On Wed, Aug 18, 2010 at 5:44 PM, Alexandru Scvorţov <span dir="ltr"><<a href="mailto:alexandru@rabbitmq.com">alexandru@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi Cal,<br>
<div class="im"><br>
> I seem to have a problem where RabbitMQ will stop accepting channel requests<br>
> after either a certain amount of messages are in the queue, or once I have<br>
> sent 200-300 connection requests.<br>
<br>
</div>What you describe is usually caused by rabbit running out memory.<br>
<br>
When rabbit runs out of memory it stops accepting new connections.<br>
Check the logs for for warnings about the hitting the high memory<br>
watermark to see if this is indeed the case.<br>
<div class="im"><br>
> At first I thought it was a memory problem, but if I restart RabbitMQ,<br>
> sometimes it will start accepting connections again and allow me to put more<br>
> items on the queue, but then other times it won't.<br>
<br>
</div>Sounds like you're squeezing in a few more messages before hitting the memory<br>
watermark again.<br>
<div class="im"><br>
> Currently, I am at 324k messages in the queue.<br>
> Does anyone have any ideas what could be causing this?<br>
<br>
</div>That's sounds like an awful lot of messages. Do you actually need all<br>
of them on the queue? Are you consuming them? (if so, are you also<br>
ack'ing them?)<br>
<br>
The problem you're facing is that the released versions of rabbit hold<br>
all of the messages in memory. As a direct consequence, how many<br>
messages you can hold in the broker is upper-bounded by the amount of<br>
RAM you have (the default is 0.4 of the available RAM, if I remember<br>
correctly). This has been fixed on the default branch (i.e. the amount<br>
of messages is upper-bounded by disk-space) and will be in the next<br>
release.<br>
<br>
Hope this helps.<br>
<br>
Cheers,<br>
Alex<br>
</blockquote></div><br><br clear="all"><br>-- <br><p style="color:rgb(0, 51, 102);font-weight:bold"><span style="border-collapse:separate;font-family:arial;line-height:normal;font-size:small">Cal Leeming</span></p><p style="color:rgb(0, 51, 102);font-weight:bold">
Operational Security & Support Team<br></p><p style="border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:rgb(204, 204, 204);padding-bottom:25px"><b>Out of Hours: </b>+44 (07534) 971120 | <b>Support Tickets: </b><a href="mailto:support@simplicitymedialtd.co.uk" style="color:rgb(49, 132, 173)" target="_blank">support@simplicitymedialtd.co.uk</a> <br>
<b>Fax: </b>+44 (02476) 578987 | <b>Email: </b><a href="mailto:cal.leeming@simplicitymedialtd.co.uk" style="color:rgb(49, 132, 173)" target="_blank">cal.leeming@simplicitymedialtd.co.uk</a> </p><div><span style="line-height:13px;font-size:10px;color:rgb(185, 184, 184)">Simplicity Media Ltd. All rights reserved.<br>
</span></div><div><span style="line-height:13px;font-size:10px;color:rgb(185, 184, 184)">Registered company number 7143564<span></span><span></span></span></div><br>
</div>