[rabbitmq-discuss] Connection(s) internally being closed !

Tim Watson watson.timothy at gmail.com
Mon Jun 10 15:27:22 BST 2013

It can take "quite a while" for the operati system to notice that a peer socket has disappeared. Consider turning on AMQP heartbeats to alleviate this delay somewhat.


On 10 Jun 2013, at 12:30, reddylast <reddylast at gmail.com> wrote:

> Hi,
> If a consumer is consuming messages from a queue and suddenly someone
> restarts rabbitmq sever (or internal network fails) then consumer stops
> consuming messages and but it doesn't throw any exception. As the consumer
> has already lost the connection so there is no way it can consume more
> messages from queues. I don't understand why a consumer is not halting whole
> process if it has lost the connection ? is there a way to do that ?
> Thanks,
> Readdy
> --
> View this message in context: http://rabbitmq.1065348.n5.nabble.com/Connection-s-internally-being-closed-tp27307.html
> Sent from the RabbitMQ mailing list archive at Nabble.com.
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list