Bug 1041575 - Python client deletes subscription queue even if it was declared to not be exclusive
Summary: Python client deletes subscription queue even if it was declared to not be ex...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: python-qpid
Version: 2.3
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: 2.4.4
: ---
Assignee: Gordon Sim
QA Contact: Leonid Zhaldybin
URL:
Whiteboard:
Depends On: 1041574
Blocks: 1024651
TreeView+ depends on / blocked
 
Reported: 2013-12-12 17:52 UTC by Gordon Sim
Modified: 2016-04-26 16:33 UTC (History)
6 users (show)

Fixed In Version: python-qpid-0.18-6
Doc Type: Bug Fix
Doc Text:
Cause: On closing a receiver with an exchange as its source, the library would issue a delete for the subscription queue, even if the queue was declared to be non-exclusive. Consequence: A shared subscription queue would be deleted when the first subscriber cancelled. Fix: The delete is not issued unless the queue s exclusive. Result: Shared subscriptions work as expected.
Clone Of: 1041574
Environment:
Last Closed: 2014-02-11 08:29:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA QPID-4903 0 None None None Never
Red Hat Product Errata RHBA-2014:0130 0 normal SHIPPED_LIVE Red Hat Enterprise MRG Messaging 2 update 2014-02-11 13:27:57 UTC

Description Gordon Sim 2013-12-12 17:52:27 UTC 
+++ This bug was initially created as a clone of Bug #1041574 +++

"""
This is an issue with the python client. It is issuing an explicit delete when closing the link, regardless of whether the subscription queue is exclusive or not.
"""

More info at https://issues.apache.org/jira/browse/QPID-4903

--- Additional comment from Justin Ross on 2013-12-12 12:51:11 EST ---

https://svn.apache.org/r1490240
Comment 4 Leonid Zhaldybin 2014-01-23 12:37:38 UTC 
Tested on RHEL5.10 and RHEL6.5 (both i386 and x86_64). This issue has been fixed.

Packages used for testing:

RHEL5.10
python-qpid-0.18-8.el5_10
python-qpid-qmf-0.18-20.el5_10
qpid-cpp-client-0.18-20.el5_10
qpid-cpp-client-devel-0.18-20.el5_10
qpid-cpp-client-devel-docs-0.18-20.el5_10
qpid-cpp-client-rdma-0.18-20.el5_10
qpid-cpp-client-ssl-0.18-20.el5_10
qpid-cpp-server-0.18-20.el5_10
qpid-cpp-server-cluster-0.18-20.el5_10
qpid-cpp-server-devel-0.18-20.el5_10
qpid-cpp-server-ha-0.18-20.el5_10
qpid-cpp-server-rdma-0.18-20.el5_10
qpid-cpp-server-ssl-0.18-20.el5_10
qpid-cpp-server-store-0.18-20.el5_10
qpid-cpp-server-xml-0.18-20.el5_10
qpid-java-client-0.18-8.el5_9
qpid-java-common-0.18-8.el5_9
qpid-java-example-0.18-8.el5_9
qpid-jca-0.18-8.el5
qpid-jca-xarecovery-0.18-8.el5
qpid-jca-zip-0.18-8.el5
qpid-qmf-0.18-20.el5_10
qpid-qmf-devel-0.18-20.el5_10
qpid-tests-0.18-2.el5
qpid-tools-0.18-10.el5_9
rh-qpid-cpp-tests-0.18-20.el5_10
ruby-qpid-qmf-0.18-20.el5_10

RHEL6.5
python-qpid-0.18-8.el6
python-qpid-qmf-0.18-20.el6
qpid-cpp-client-0.18-20.el6
qpid-cpp-client-devel-0.18-20.el6
qpid-cpp-client-devel-docs-0.18-20.el6
qpid-cpp-client-rdma-0.18-20.el6
qpid-cpp-client-ssl-0.18-20.el6
qpid-cpp-server-0.18-20.el6
qpid-cpp-server-cluster-0.18-20.el6
qpid-cpp-server-devel-0.18-20.el6
qpid-cpp-server-ha-0.18-20.el6
qpid-cpp-server-rdma-0.18-20.el6
qpid-cpp-server-ssl-0.18-20.el6
qpid-cpp-server-store-0.18-20.el6
qpid-cpp-server-xml-0.18-20.el6
qpid-java-client-0.18-8.el6_4
qpid-java-common-0.18-8.el6_4
qpid-java-example-0.18-8.el6_4
qpid-jca-0.18-8.el6
qpid-jca-xarecovery-0.18-8.el6
qpid-jca-zip-0.18-8.el6
qpid-qmf-0.18-20.el6
qpid-qmf-devel-0.18-20.el6
qpid-tests-0.18-2.el6
qpid-tools-0.18-10.el6_4
rh-qpid-cpp-tests-0.18-20.el6
ruby-qpid-qmf-0.18-20.el6

-> VERIFIED
Comment 6 errata-xmlrpc 2014-02-11 08:29:10 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0130.html
Note You need to log in before you can comment on or make changes to this bug.