Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. create several queues against a single cluster node all or some of which have a limit configured 2. bind these queues to e.g. amq.topic all with the same key 3. start a new cluster node member 4. send some messages through the exchange to those queues; cause one (but not all) of the queues to reach its capacity (e.g. have receivers on all queues but stop the receiver for one queue) 5. when the sender hits the capacity limit on that one queue, the number of queues to which the final message was enqueued depends on binding order which is now inconsistent 6. run qpid-stat -q against each nod e to check for inconsistency E.g. 1. start node 1 2. for q in b d c a ; do qpid-config add queue $q --max-queue-count 5; qpid-config bind amq.topic $q key; done 3. start node 2 4. qpid-send --messages 4 --address amq.topic/key 5. for q in a b d; do ./examples/messaging/drain --count 4 $q; done Actual results: Inconsistency in messages on queues Expected results: No inconsistency Additional info:
Upstream fix on trunk r1092765
r1092765 broke the trunk tests and was reverted by r1092804. Will post again when the problems are fixed.
Upstream fix on trunk r1094734
Committed to release repository: http://mrg1.lab.bos.redhat.com/cgit/qpid.git/commit/?h=mrg_2.0.x&id=5d4396ac04425f870a9670b5168836980ea2aabd
*** Bug 692906 has been marked as a duplicate of this bug. ***
This issue has been fixed in qpid-cpp-mrg-0.10-4 for RHEL5, but not yet available in any RHEL6 package. The bug was cloned for RHEL6: please see bug 705802 Verified on RHEL5.6 architectures: i386, x86_64 packages installed: python-qpid-0.10-1.el5 python-qpid-qmf-0.10-6.el5 qpid-cpp-client-0.10-7.el5 qpid-cpp-client-devel-0.10-7.el5 qpid-cpp-client-devel-docs-0.10-7.el5 qpid-cpp-client-ssl-0.10-7.el5 qpid-cpp-server-0.10-7.el5 qpid-cpp-server-cluster-0.10-7.el5 qpid-cpp-server-devel-0.10-7.el5 qpid-cpp-server-ssl-0.10-7.el5 qpid-cpp-server-store-0.10-7.el5 qpid-cpp-server-xml-0.10-7.el5 qpid-java-client-0.10-6.el5 qpid-java-common-0.10-6.el5 qpid-java-example-0.10-6.el5 qpid-qmf-0.10-2.el5 qpid-qmf-0.10-6.el5 qpid-qmf-devel-0.10-2.el5 qpid-qmf-devel-0.10-6.el5 qpid-tools-0.10-5.el5 rh-qpid-cpp-tests-0.10-7.el5 rh-tests-distribution-MRG-Messaging-qpid_common-1.6-56 ruby-qpid-qmf-0.10-6.el5 -> VERIFIED
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/RHEA-2011-0890.html