[rabbitmq-discuss] RabbitMQ AMQP :- Socket error: Broken pipe on high load
Michael Klishin
michael.s.klishin at gmail.com
Sun Apr 7 20:45:58 BST 2013
2013/4/7 <dharmanshu at ophio.co.in>
> And 1 reader that publishes messages using a for loop.
>
> After publishing around 120,000 messages , the reader gives out the
> following error on publish.
>
> Socket error: Broken pipe.
>
> The reader process then needs to be killed manually and the broker needs
> to be restarted.
> Any idea how to handle this ?
>
What is in RabbitMQ log? Your publisher is likely to be blocked because you
are going
above the RAM watermark (or even disk, on a small partition, for example).
It will be unblocked when consumers catch up and drain some messages to
free up resources.
The client should not fail with a socket error, though.
--
MK
http://github.com/michaelklishin
http://twitter.com/michaelklishin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130407/4a74d486/attachment.htm>
More information about the rabbitmq-discuss
mailing list