[rabbitmq-discuss] Server connections not closing

Emile Joubert emile at rabbitmq.com
Thu Nov 10 10:28:38 GMT 2011

Hi Robert,

On 10/11/11 04:31, Robert Gilland wrote:
>> Is there any device on the network that intermediates between the broker
>> and client, and potentially keeping the server connections open?
> Yes There are 4 hops on the traceroute between the client and server
> machine. according to our network guy. So it is failing on the WAN.
>> Do you
>> get the same issue if the broker and client run on the same server
>> (using localhost)?
> On local LAN between my machine and the server machine. all
> connections are being closed successfully.

If the problem can only be reproduced over the WAN then I strongly
suspect the problem is with the WAN. Unless there is any AMQP-specific
configuration you should be able to reproduce the problem with other

> There must be some process not happening to close a connection at the
> RabbitMQ server machine.
> Something must be failing to get across the network. so the system is
> failing to close it's connections.

The RabbitMQ server uses sockets in the same way as any application.
(Nagle is turned off by default). The connection teardown is done by the
TCP stack as implemented in your OS. If there is something that you
believe RabbitMQ should be doing differently then let us know.


More information about the rabbitmq-discuss mailing list