[rabbitmq-discuss] RabbitMQ blocking issue

Thu Feb 7 23:00:29 GMT 2013

We have an issue with our RabbitMQ clients not publishing to our RabbitMQ server. We see that the client hangs approx. every 2 hours and never recovers.

Versions:
Client: amqp-client-2.8.7.jar  , spring-amqp-1.1.1.RELEASE.jar
server: noarch/rabbitmq-server-2.8.7-1.noarch.rpm

On the client side we see that our application stops working. When we query the port we see:
[pkonar at ajtrafp067 ~]$ netstat -an | grep 5672
tcp        0 194017 ::ffff:10.196.42.93:47657   ::ffff:10.196.42.43:5672    FIN_WAIT1
tcp        0   2722 ::ffff:10.196.42.93:46361   ::ffff:10.196.42.43:5672    ESTABLISHED

The FIN_WAIT1 is from the application restart and never recovers the port. Meaning never releases the port from FIN_WAIT1. After restarting the application we see a new connection created the works, but we would prefer not restarting the app every 2 hours.

Server side
 [pkonar at ajtrafp017 ~]$ sudo rabbitmqctl list_connections name last_blocked_age last_blocked_by Listing connections ...
10.196.42.90:35923 -> 10.196.42.43:5672 497412.591327   flow
10.196.42.93:46361 -> 10.196.42.43:5672 912.850887      flow
10.196.42.92:45603 -> 10.196.42.43:5672 912.554772      flow
10.196.42.94:46145 -> 10.196.42.43:5672 319388.635685   flow
10.196.42.93:47657 -> 10.196.42.43:5672 83830.533463    flow
10.196.42.94:44100 -> 10.196.42.43:5672 10568.909981    flow
10.196.42.94:33175 -> 10.196.42.43:5672 166511.852811   flow
10.196.42.91:56200 -> 10.196.42.43:5672 912.849807      flow
10.196.42.90:40466 -> 10.196.42.43:5672 126071.593769   flow
10.196.42.90:56644 -> 10.196.42.43:5672 912.628977      flow
...done.

Looking for any help possible.

Thanks
Peter Konar

The information contained in this communication may be CONFIDENTIAL and is intended only for the use of the recipient(s) named above.  If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited.  If you have received this communication in error, please notify the sender and delete/destroy the original message and any copy of it from your computer or paper files.