Red Hat Bugzilla – Bug 481206
Connection shut-down hang on clustered brokers
Last modified: 2015-11-15 20:18:43 EST
There is an intermittent hang on client-connection shutdown occurring between the Python client and clustered c++ brokers. Presumably, this will happen with other clients as well.
This has never been seen on a stand-alone broker.
The trace shows the following:
|-- conn.close -------------> |
| <--------- conn.close-ok -- |
From this point forward, the client is waiting for the TCP connection to close. The TCP connection remains in the ESTABLISHED state (via netstat -t).
The server sends a conn.close-ok but does not close the TCP socket.
This is intermittent. On a continuous run, it will run correctly for dozens of times before causing a hang.
The Python client has been fixed as of rev 736742 to close the socket on receipt of a close-ok. This fixes the shutdown hang but there may still be an issue on the broker side.
Ted, this one's quite old. Does it describe still existing problem?
I assume not since there hasn't been an update since early 2009.