Bug 631969
| Summary: | Rdma client can hang on exit under rare circumstances | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Andrew Stitcher <astitcher> | |
| Component: | qpid-cpp | Assignee: | Andrew Stitcher <astitcher> | |
| Status: | CLOSED ERRATA | QA Contact: | ppecka <ppecka> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | beta | CC: | freznice, gsim, iboverma, jneedle, tross | |
| Target Milestone: | 1.3.2-RC1 | |||
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | qpid-cpp-mrg-0.7.946106-26 | Doc Type: | Bug Fix | |
| Doc Text: |
Rarely clients using the RDMA transport could hang if the broker abruptly disconnects.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 631973 (view as bug list) | Environment: | ||
| Last Closed: | 2011-02-15 12:13:39 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: | ||||
|
Description
Andrew Stitcher
2010-09-08 19:03:34 UTC
It appears that in this rare case something prevents the shutdownHandler from being called in ConnectionImpl so that it doesn't know that the connection has gone away. It seems that at least one possibility for this hang is when the rdma disconnects happen very early in the lifetime of the connection, perhaps even before connection establishment This hang seems to have been fixed by the bug fixing work on BZ631973. It no longer exhibits Fixed on trunk Tested fix without hang for 24 hours. Checked into 1.3 branch
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Rarely clients using the RDMA transport could hang if the broker abruptly disconnects.
It's not clear to me whether this is the same bug or a different one. However I believe that this issue should also be fixed by the same set of changes. It looks to me that you were reproducing the bug rather than establishing its absence, so if you see this problem in the item under test please raise it as a new bug. (In reply to comment #8) > It looks to me that you were reproducing the bug rather than establishing its > absence, so if you see this problem in the item under test please raise it as a > new bug. yes, exactly - this happened when I tried to reproduce this issue continuously tested for 3days, verified with: # rpm -qa | grep -Ei '(qpid)' | sort -u python-qpid-0.7.946106-14.el5 qpid-cpp-client-0.7.946106-26.el5 qpid-cpp-client-devel-0.7.946106-26.el5 qpid-cpp-client-devel-docs-0.7.946106-26.el5 qpid-cpp-client-rdma-0.7.946106-26.el5 qpid-cpp-client-ssl-0.7.946106-26.el5 qpid-cpp-mrg-debuginfo-0.7.946106-26.el5 qpid-cpp-server-0.7.946106-26.el5 qpid-cpp-server-cluster-0.7.946106-26.el5 qpid-cpp-server-devel-0.7.946106-26.el5 qpid-cpp-server-rdma-0.7.946106-26.el5 qpid-cpp-server-ssl-0.7.946106-26.el5 qpid-cpp-server-store-0.7.946106-26.el5 qpid-cpp-server-xml-0.7.946106-26.el5 qpid-java-client-0.7.946106-14.el5 qpid-java-common-0.7.946106-14.el5 qpid-java-example-0.7.946106-14.el5 qpid-tools-0.7.946106-11.el5 --> VERIFIED An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0217.html |