[rabbitmq-discuss] Rabbitmq 2.5-2.6.1 java hanging on close of connection

Matthias Radestock matthias at rabbitmq.com
Tue Jan 15 23:30:26 GMT 2013


On 15/01/13 20:55, Sankalp Acharya wrote:
> Incidentally, we figured out what the problem is.

Glad to hear that.

> It seems that the connection blocking, in turn, /also/ blocks close
> requests from being ack'd! This certainly seems like a bug to me – I'm
> not sure why the server should deny already-connected clients the
> ability to close their connections.

Connection blocking happens at the tcp level since that's the only way 
the broker can make sure it will not be receiving any more messages 
regardless of what the client is doing.

Consequently the AMQP connection.close command will not be received by 
the broker either. There's nothing we can do about that at the broker end.

Clients could have some sort of timeout for these situations, but few 
client libraries support that.



More information about the rabbitmq-discuss mailing list