[rabbitmq-discuss] Fw: Exception on TCP connection

[Simon MacMullen]

Hi Dave.

Yes, the Java client should shut down after two missed heartbeats. I've 
just tested this with 2.1.1 and 1.8.1 clients against a 2.1.1 server and 
it worked for me; although there is a remark in the 2.1.1 release notes:

  - move heartbeat sender into a separate thread to ensure that missing
    heartbeats are detected promptly in all cases

Cheers, Simon

On 05/11/10 16:58, Dave Greggory wrote:
> Sending to the list...
>
>
>
> ----- Forwarded Message ----
> From: Dave Greggory<davegreggory at yahoo.com>
> To: Michael Bridgen<mikeb at rabbitmq.com>
> Sent: Fri, November 5, 2010 12:57:30 PM
> Subject: Re: [rabbitmq-discuss] Exception on TCP connection
>
> No the connection does not get closed and the shutdown event never fires.
>
> We enabled AMQP heartbeats (@ 30 seconds), just for the purpose of early
> detection of connection trouble.
>
> See http://old.nabble.com/Shutdown-Listener-on-Java-Client-API-td29699374.html
>
> So is the normal behavior for connection to shutdown and the shutdown event to
> fire when 2 heartbeats are missed? What could be preventing that?
>
>
>
>
> ----- Original Message ----
> From: Michael Bridgen<mikeb at rabbitmq.com>
> To: rabbitmq-discuss at lists.rabbitmq.com
> Sent: Fri, November 5, 2010 7:18:01 AM
> Subject: Re: [rabbitmq-discuss] Exception on TCP connection
>
> Hi Dave,
>
>> Every once in a while we notice this error in our RabbitMQ logs. Any idea what
>> this means?
>>
>>    =ERROR REPORT==== 2-Nov-2010::19:37:31 ===
>> exception on TCP connection<0.10945.3>   from 192.168.210.9:14189
>> {timeout,running}
>
> It indicates missed heartbeats.
>
> Have a look here:
> http://old.nabble.com/Unexplained-shutdown-of-RabbitMQ-td28558360.html
>
> and here:
> http://forum.trapexit.org/mailinglists/viewtopic.php?t=16662&sid=9c5323df7c6a6b8cf28ffc9ba6c34fd6
>
>
>
>> We run 2 RabbitMQ 2.0 nodes unclustered, sitting behind a load balancer.  Only
>
>> 1
>> RabbitMQ node active at a time in the load balancer. Second one  is there
>> mainly
>> for failing over to.
>>
>>
>> When this happens the shutdown listener on the Java Client API does not fire
> in
>> spite of having AMQP Heartbeats enabled.
>
> Does the connection actually get closed though?  If I recall correctly,
> connections will only be forcibly closed if a client misses a number of
> heartbeats in a row (two I think).
>
>
> Michael
>
>> There are no other significant entries
>> in the logs. Just the standard "starting TCP connection",  "closing TCP
>> connection", "accepted TCP connection" and "connection_closed_abruptly"
> entries
>> (Connection closed abruptly is just the load balancer checking whether Rabbit
>> node is alive).
>>
>>
>>
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss


-- 
Simon MacMullen
Staff Engineer, RabbitMQ
SpringSource, a division of VMware