Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 576693

Summary: qpid-cluster -d does not close the client connection
Product: Red Hat Enterprise MRG Reporter: Mike Cressman <mcressma>
Component: qpid-qmfAssignee: Alan Conway <aconway>
Status: CLOSED ERRATA QA Contact: Frantisek Reznicek <freznice>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.2CC: aconway, esammons, freznice, tao
Target Milestone: 1.3   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
The "qpid-cluster -d" command was not closing the client connection. With this update, executing "qpid-cluster -d" works as expected and closes the client connection.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-14 16:11:23 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 Mike Cressman 2010-03-24 20:57:44 UTC 
Description of problem:
qpid-cluster -d is supposed to close the client connection, but it does not


Version-Release number of selected component (if applicable):
MRG 1.2

How reproducible:
Always

Steps to Reproduce:
1. Set up a cluster of at least two brokers (can be on same machine)
2. Run 'qpid-cluster -C' to see the two brokers connected to each other
2. Connect a client application that continues to run for while
3. Run 'qpid-cluster -C' to identify the new connection (for the new client)
   e.g. localhost:46752
4. Run 'qpid-cluster -d <host>:<port>', e.g. <host>:<port>=localhost:46752
  
Actual results:
"Closing connection from client: 127.0.0.1:46752", but client is not affected and continues to run.

Expected results:
Client connection should be closed from broker end. Client should detect this and be unable to continue.
Comment 2 Alan Conway 2010-05-31 15:58:44 UTC 
This appears to have been fixed as a side effect of some other fix. It works correctly on current trunk r949767 and mrg_1.3.x branch:

http://mrg1.lab.bos.redhat.com/git/?p=qpid.git;a=commitdiff;h=ad3a7e4927edc01a262a0ee3903f55592b41d337
Comment 4 Frantisek Reznicek 2010-09-21 15:30:53 UTC 
The issue has been fixed (the connection can be cancelled/destroyed via qpid-cluster -d ), retested on RHEL 4.8 / 5.5 i386 / x86_64 on packages:
python-qmf-0.7.946106-13.el5
python-qpid-0.7.946106-14.el5
qmf-*0.7.946106-15.el5
qpid-cpp-*-0.7.946106-15.el5
qpid-dotnet-0.4.738274-2.el5
qpid-java-*-0.7.946106-9.el5
qpid-tools-0.7.946106-10.el5

-> VERIFIED
Comment 5 Frantisek Reznicek 2010-09-21 15:32:24 UTC 
(In reply to comment #4)
> The issue has been fixed (the connection can be cancelled/destroyed via
> qpid-cluster -d ), retested on RHEL 4.8 / 5.5 i386 / x86_64 on packages:
> python-qmf-0.7.946106-13.el5
> python-qpid-0.7.946106-14.el5
> qmf-*0.7.946106-15.el5
> qpid-cpp-*-0.7.946106-15.el5
> qpid-dotnet-0.4.738274-2.el5
> qpid-java-*-0.7.946106-9.el5
> qpid-tools-0.7.946106-10.el5
> 
> -> VERIFIED

-> qpid-cluster -d ), retested on RHEL 4.8 / 5.5 i386 / x86_64 on packages:
+> qpid-cluster -d ), retested on RHEL  5.5 i386 / x86_64 on packages:

as the issue is dependent on qpid-cluster which operates when clustering is enabled.
Comment 6 Martin Prpič 2010-10-07 13:46:23 UTC 
    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:
The "qpid-cluster -d" command was not closing the client connection. With this update, executing "qpid-cluster -d"  works as expected and closes the client connection.
Comment 8 errata-xmlrpc 2010-10-14 16:11:23 UTC 
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/RHSA-2010-0773.html