[rabbitmq-discuss] Exception on TCP connection

[Michael Bridgen]

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