<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">2013/4/7 <span dir="ltr"><<a href="mailto:dharmanshu@ophio.co.in" target="_blank">dharmanshu@ophio.co.in</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>And 1 reader that publishes messages using a for loop.</div><div><br></div><div>After publishing around 120,000 messages , the reader gives out the following error on publish.</div><div> </div><div>Socket error: Broken pipe.<br>
</div><div><br></div><div>The reader process then needs to be killed manually and the broker needs to be restarted. </div><div>Any idea how to handle this ?</div><div></div></blockquote></div><br>What is in RabbitMQ log? Your publisher is likely to be blocked because you are going</div>
<div class="gmail_extra">above the RAM watermark (or even disk, on a small partition, for example).</div><div class="gmail_extra"><br></div><div class="gmail_extra">It will be unblocked when consumers catch up and drain some messages to free up resources.<br>
<br clear="all"><div style>The client should not fail with a socket error, though.</div>-- <br>MK<br><br><a href="http://github.com/michaelklishin" target="_blank">http://github.com/michaelklishin</a><br><a href="http://twitter.com/michaelklishin" target="_blank">http://twitter.com/michaelklishin</a><br>
</div></div>