Bug 481206 - Connection shut-down hang on clustered brokers
Summary: Connection shut-down hang on clustered brokers
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 1.1
Hardware: All
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Andrew Stitcher
QA Contact: Eric Sammons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-01-22 19:15 UTC by Ted Ross
Modified: 2020-05-22 14:35 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-22 14:35:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ted Ross 2009-01-22 19:15:45 UTC
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.

Comment 1 Ted Ross 2009-01-22 19:19:29 UTC
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.

Comment 2 Justin Ross 2012-11-06 19:21:37 UTC
Ted, this one's quite old.  Does it describe still existing problem?

Comment 3 Ted Ross 2012-11-08 18:07:47 UTC
I assume not since there hasn't been an update since early 2009.


Note You need to log in before you can comment on or make changes to this bug.