<div class="gmail_quote">On Thu, Jul 15, 2010 at 3:19 PM, Robert Raschke <span dir="ltr"><<a href="mailto:rtrlists@googlemail.com">rtrlists@googlemail.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;">
<br><div class="gmail_quote">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>
<div>
<br>Otherwise your sending of persistent message will eventually make Rabbit run out of resources.<br></div></div><br>Robby<br><br></blockquote><div><br>well, I think RabbitMQ server should have (and it probably does?) means to stop accepting messages from the producer before it enters the inconsistent and unrecoverable state. Because in many applications server can not expect to have cooperative and well behaved producers, and it should be able to survive such situations without going down.<br>
<br>davorin rusevljan<br><a href="http://www.cloud208.com/">http://www.cloud208.com/</a><br><br></div></div>