Bug 693444

Summary:	Inconsistency in clients on reliability of receiver link from exchange
Product:	Red Hat Enterprise MRG	Reporter:	Gordon Sim <gsim>
Component:	python-qpid	Assignee:	Gordon Sim <gsim>
Status:	CLOSED ERRATA	QA Contact:	Petr Matousek <pematous>
Severity:	high	Docs Contact:
Priority:	high
Version:	1.3	CC:	dkinon, freznice, hpetty, iboverma, jross, pematous
Target Milestone:	2.2
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-qpid-0.14-7.el5	Doc Type:	Bug Fix
Doc Text:	Cause Previously there was an inconsistent behaviour between the python and c++ versions of the messaging API with respect to the default reliability of receivers. Consequence This led to confusion for users involved with both APIs as well as making documentation more complicated. Change The python client was modified to have the same default reliability for topics (i.e. for cases where the node the receiver is established from is an exchange. (All other cases were already in alignment). Result When establishing a receiver from an exchange (i.e. a topic pattern), the link will be unreliable by default. This can be changed if required by setting the reliability option within the link options of the address.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-09-19 17:20:06 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 Gordon Sim 2011-04-04 17:25:22 UTC

In python by default the subscription queue created for a receiver on an exchange is non-auto-deleted. On c++ however it *is* auto deleted unless you specify the link to be reliable.

Should resolve inconsistency.

Comment 1 Gordon Sim 2012-04-11 12:05:27 UTC

Fixed upstream: http://svn.apache.org/viewvc?view=rev&rev=1324719

Comment 6 Petr Matousek 2012-07-19 12:37:39 UTC

This issue has been fixed.

Tested on RHEL5.8 and RHEL6.3 (i386 and x86_64).

Packages used for testing:
python-qpid-0.14-7.el5
python-qpid-0.14-9.el6_3

-> VERIFIED

Comment 7 Gordon Sim 2012-08-06 08:38: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:
Cause
   Previously there was an inconsistent behaviour between the python and c++ versions of the messaging API with respect to the default reliability of receivers.

Consequence
  This led to confusion for users involved with both APIs as well as making documentation more complicated.   

Change
  The python client was modified to have the same default reliability for topics (i.e. for cases where the node the receiver is established from is an exchange. (All other cases were already in alignment).

Result
  When establishing a receiver from an exchange (i.e. a topic pattern), the link will be unreliable by default. This can be changed if required by setting the reliability option within the link options of the address.

Comment 9 errata-xmlrpc 2012-09-19 17:20:06 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/RHSA-2012-1277.html