[rabbitmq-discuss] Some problem about connection_closed_abruptly

Tim Watson watson.timothy at gmail.com
Thu Nov 1 10:07:21 GMT 2012


Any

Sent from my iPhone.

On 1 Nov 2012, at 05:15, andy lin <oldhomelh at gmail.com> wrote:

> Now a new error has occured .The server's log record the error : 
> connection_closed_abruptly,I find my consumer keeping the state of
> connecting,but it can't receive any message.What is the problem ? 
> 
> 

From what you're saying, it sounds a lot to me like the network link between the two machines is broken. Normally you'd expect the client application to notice that the socket is no longer available, but the underlying tcp stack can spend quite some time attempting to retry sending before it gives up and returns an error code on the socket. We've observed this behaviour during disconnection when clients waiting for the server to return connection.close_ok can be stuck for up to 20 minutes or so. It sounds like you're seeing something similar to me.

What client are you using? Have you considered enabling heartbeats?

> 
> --
> View this message in context: http://rabbitmq.1065348.n5.nabble.com/Some-problem-about-connection-closed-abruptly-tp23032.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