[rabbitmq-discuss] Problem while one of clients crashes.
rabbitmq at o2.pl
Sun May 8 08:48:20 BST 2011
I'm using rabbit version 1.7.1 I've observed a strange behavior. When i have two consumers (A,B) and one of them (A) is closed unexpectedly (so without closing channel etc - for example forced shutdown) than the server still shows that two clients are connected, and is trying to send message to this terminated client (A).This results in having unacknowledged message in the queue. In most cases after some time this connection is timed out and message is returned to queue and processed by the other client (B). But it also often happens that even though connection is timed out the unacknowledged message still remains and is blocking the other client (B). Other messages are waiting in the queue unconsumed. When new client (C) is connected to server then all waiting massages are consumed by the new client. So there are two clients again (B,C). Now when the old client (B) is being closed and disconnected from server , this unacknowledged message remains and starts blocking remaining client (C). Messages are stuck in queue.
What could be the reason of such behavior? Maybe it is a known bug? Maybe some walk-arounds?
I really would appreciate any ideas and solutions.
Thanks in advance.
More information about the rabbitmq-discuss