[rabbitmq-discuss] Delay delivering messages

Matthew Sackman matthew at rabbitmq.com
Sat Sep 18 23:34:07 BST 2010

On Thu, Sep 16, 2010 at 09:01:17AM +0100, Michael Burns wrote:
> I've noticed sometimes that there are extra connections hanging about on the
> RabbitMQ broker (using rabbitmqctl  list_connections).
> It's possible sometimes in our consumers that we are not always closing the
> connection cleanly (sometimes people are simply killing their app rather
> than shutting down cleanly).
> Could this somehow explain why we experience these delays?

Yes. If the TCP socket is still alive then Rabbit will not believe the
connection has died, and so will not make unacknowledged messages
available to other consumers.

It would seem that this is your problem. To ensure that the connection
is promptly detected to be detached, you could either turn on AMQP
heartbeats or TCP KeepAlive. Either should suffice.


More information about the rabbitmq-discuss mailing list