[rabbitmq-discuss] dead connection lingers around?
simon at rabbitmq.com
Mon Feb 27 11:05:56 GMT 2012
Sometimes if a TCP connection gets killed outright the OS never notices
and so we don't know either.
This probably implies you are not closing connections properly? (i.e.
with the AMQP close handshake, by invoking amqp_connection:close/1.)
Enabling AMQP heartbeats will allow RabbitMQ to detect this condition.
On 27/02/12 09:25, stone wrote:
> Have a problem while testing my Erlang client based application.
> I have no idea if it's due to some bad behavior in my app or whatsoever,
> hope I can get some useful information here.
> In my case, I have:
> three rabbit nodes in a cluster;
> one non-durable topic exchange;
> two connections established;
> several channels and queues (exclusive & non-exclusive) declared.
> While i'm testing, sometimes the connections they just linger around
> even the client has quit already.
> For instance, here is one or my dead connections (copied from admin page):
> AMQP 0-9-1 10.15.36.246:36526 <http://10.15.36.246:36526>
> rabbit at test-app2 0B/s_(1.9kB total) 0B/s_(1.1kB total) 4 guest running
> I'm pretty sure that the client on 10.15.36.246 has been killed already,
> but the connection is still in "running" state.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss