[rabbitmq-discuss] connection closed abruptly errors on logs

[David Wragg]

Hi Dave,

Dave Greggory <davegreggory at yahoo.com> writes:
> I configured my 2 node cluster to behind a load balancer that round robins to 
> the two nodes. Once I did that, I started noticing these errors in RabbitMQ 
> logs.
>
> [...]
>
> =INFO REPORT==== 23-Jul-2010::10:27:14 ===
> accepted TCP connection on 0.0.0.0:5672 from <loadbalancer_ip>:1706
>
> =INFO REPORT==== 23-Jul-2010::10:27:14 ===
> starting TCP connection <0.3879.4> from <loadbalancer_ip>:1706
>
> =WARNING REPORT==== 23-Jul-2010::10:27:14 ===
> exception on TCP connection <0.3879.4> from <loadbalancer_ip>:1706
> connection_closed_abruptly
>
> [...]
>
> Messages sent to RabbitMQ are being handled properly and consumers seem to be 
> receiving them just fine. What do these errors mean?

That is caused by clients disconnecting without following the proper
AMQP shutdown protocol, e.g. they simply close the socket instead of
sending a "connection.close" command and waiting for
"connection.close_ok".

Given the timestamps in the logs above, it looks like the load balancer
is connecting, and then promptly closing the connection.  This is
probably the load balancer probing to check that the nodes are available
from connections.  If so, they are nothing to worry about.

David

-- 
David Wragg
Staff Engineer, RabbitMQ
SpringSource, a division of VMware