Description of problem: While concurrently creating bindings to the same queue from multiple broker connections, the broker will periodically crash. Version-Release number of selected component (if applicable): qpid-cpp-server-0.12-6_ptc_hotfix_3.el6.x86_64 How reproducible: Frequently Steps to Reproduce: 1. Concurrently create bindings to the same queue 2. Observe that multiple threads are able to invoke QueueBindings::add concurrently Actual results: Qpid broker will crash Expected results: Qpid broker does not crash and bindings are created Additional info:
Upstream issue: https://issues.apache.org/jira/browse/QPID-3755
Created attachment 555091 [details] Reproducer
I've attached a reproducer. This program runs against a broker running on "localhost:10000" and has a queue called "test-queue" pre-configured. If 20 instances of this program are run at the same time, the failure can be seen reliably.
Fixed upstream in revision 1231158.
*** Bug 704510 has been marked as a duplicate of this bug. ***
Tested on RHEL5.9 and RHEL6.3 (both i386 and x86_64). This issue has been fixed. Packages used for testing: RHEL5.9 qpid-cpp-client-0.18-13.el5 qpid-cpp-client-devel-0.18-13.el5 qpid-cpp-client-devel-docs-0.18-13.el5 qpid-cpp-client-ssl-0.18-13.el5 qpid-cpp-server-0.18-13.el5 qpid-cpp-server-cluster-0.18-13.el5 qpid-cpp-server-devel-0.18-13.el5 qpid-cpp-server-ssl-0.18-13.el5 qpid-cpp-server-store-0.18-13.el5 qpid-cpp-server-xml-0.18-13.el5 qpid-java-client-0.18-6.el5 qpid-java-common-0.18-6.el5 qpid-java-example-0.18-6.el5 qpid-qmf-0.18-13.el5 qpid-qmf-devel-0.18-13.el5 qpid-tools-0.18-7.el5 RHEL6.3 qpid-cpp-client-0.18-13.el6 qpid-cpp-client-devel-0.18-13.el6 qpid-cpp-client-devel-docs-0.18-13.el6 qpid-cpp-server-0.18-13.el6 qpid-cpp-server-devel-0.18-13.el6 qpid-cpp-server-store-0.18-13.el6 qpid-cpp-server-xml-0.18-13.el6 qpid-java-client-0.18-6.el6 qpid-java-common-0.18-6.el6 qpid-java-example-0.18-6.el6 qpid-qmf-0.18-13.el6 qpid-tools-0.18-7.el6_3 -> 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/RHSA-2013-0561.html