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.
Fixed upstream: http://svn.apache.org/viewvc?view=rev&rev=1324719
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
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.
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