Bug 481206
| Summary: | Connection shut-down hang on clustered brokers | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Ted Ross <tross> |
| Component: | qpid-cpp | Assignee: | Andrew Stitcher <astitcher> |
| Status: | CLOSED WONTFIX | QA Contact: | Eric Sammons <esammons> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 1.1 | CC: | aconway, astitcher, cctrieloff, gsim, jross, tross |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-05-22 14:35:01 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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. |
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: Client Server | | |-- 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.