Moving this for 2.4 for verification.

It is quite hard to directly observe the problem as it affects state largely hidden within the broker. One way would be to use https://bugzilla.redhat.com/show_bug.cgi?id=703600 to indirectly observe it. If you sent a message to an auto-delete queue, then fetched it from a client, closed the receiver and *released* the message rather than acknowledging it, then where the bug persists the queue would remain visible to e.g. qpid-stat whereas when the bug was fixed it should disappear.

In theory for a large number of messages the broker memory would also grow, but that is harder to tie directly to one source.

Tested on RHEL5.9 and RHEL6.4 (both i386 and x86_64). This issue has been fixed.

Packages used for testing:

RHEL5.9:
python-qpid-0.22-4.el5
python-qpid-qmf-0.22-6.el5
qpid-cpp-client-0.22-7.el5
qpid-cpp-client-devel-0.22-7.el5
qpid-cpp-client-devel-docs-0.22-7.el5
qpid-cpp-client-ssl-0.22-7.el5
qpid-cpp-server-0.22-7.el5
qpid-cpp-server-devel-0.22-7.el5
qpid-cpp-server-ha-0.22-7.el5
qpid-cpp-server-ssl-0.22-7.el5
qpid-cpp-server-store-0.22-7.el5
qpid-cpp-server-xml-0.22-7.el5
qpid-proton-c-0.4-2.2.el5
qpid-qmf-0.22-6.el5
qpid-qmf-devel-0.22-6.el5
qpid-tools-0.22-2.el5

RHEL6.4:
python-qpid-0.22-4.el6
python-qpid-qmf-0.22-6.el6
qpid-cpp-client-0.22-7.el6
qpid-cpp-client-devel-0.22-7.el6
qpid-cpp-client-devel-docs-0.22-7.el6
qpid-cpp-server-0.22-7.el6
qpid-cpp-server-devel-0.22-7.el6
qpid-cpp-server-ha-0.22-7.el6
qpid-cpp-server-store-0.22-7.el6
qpid-cpp-server-xml-0.22-7.el6
qpid-proton-c-0.4-2.2.el6
qpid-qmf-0.22-6.el6
qpid-tools-0.22-3.el6

-> VERIFIED

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/RHEA-2014-1296.html