<br><div class="gmail_quote">On Thu, Jul 15, 2010 at 12:58 PM, Ovidiu Deac <span dir="ltr"><<a href="mailto:ovidiudeac@gmail.com">ovidiudeac@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
...and the erlang version is "R13B01"<br>
<div><div></div><div class="h5"><br>
On Thu, Jul 15, 2010 at 2:53 PM, Ovidiu Deac <<a href="mailto:ovidiudeac@gmail.com">ovidiudeac@gmail.com</a>> wrote:<br>
> I forgot to say that we are using rabbitmq 1.8.0 on linux.<br>
><br>
> On Thu, Jul 15, 2010 at 2:40 PM, Ovidiu Deac <<a href="mailto:ovidiudeac@gmail.com">ovidiudeac@gmail.com</a>> wrote:<br>
>> We are testing a rabbitmq intalation to see how it behaves if there is<br>
>> no consumer while the producer publishes messages. The point of the<br>
>> test is to see what we can rely on if somehow our consumer processes<br>
>> die.<br>
>><br>
>> In order to do this we send persistent messages with a 300bytes<br>
>> content in a loop and after 200k messages rabbitmq uses 100% processor<br>
>> and is unreachable. The memory usage on the machine is only 27%. Even<br>
>> when restarting the broker it won't start anymore.<br>
>><br>
>> Any ideas how I can tune rabbitmq to deal with this situation?<br>
>><br>
>> Thanks,<br>
>> Ovidiu<br>
>><br>
><br>
<br></div></div></blockquote><div><br>I think you should use some flow control. If your Rabbit has the memory alerts turned on, then your producer can pick up the channel.flow/active=false and stop sending until you get the active=true.<br>
<br>Otherwise your sending of persistent message will eventually make Rabbit run out of resources.<br></div></div><br>Robby<br><br>