Description of problem: If a durable queue is set to use a ring policy, and if concurrent publication causes persistent messages to be evicted from the queue, a deadlock is possible. Version-Release number of selected component (if applicable): Since 1.1 How reproducible: Easily Steps to Reproduce: 1. start broker with store loaded 2. create durable queue with ring policy and particular limit (e.g. qpid-config add queue test-queue --durable --limit-policy ring --max-queue-count 5) 3. start two or more publishers sending durable messages to that queue (e.g. 2x while sender --durable true < messages.in; do true; done) Actual results: broker eventually hangs Expected results: should continue indefinitly with no hangs
Created attachment 348929 [details] Fix
Fixed in qpidd-0.5.752581-20.
The issue has been fixed, validated on RHEL 4.7 / 5.3, i386 / x86_64 on packages: [root@mrg-qe-02 bz509096]# rpm -qa | grep -E '(qpid|openais|rhm)' | sort -u openais-0.80.3-22.el5_3.8 openais-debuginfo-0.80.3-22.el5_3.8 python-qpid-0.5.752581-3.el5 qpidc-0.5.752581-22.el5 qpidc-debuginfo-0.5.752581-22.el5 qpidc-devel-0.5.752581-22.el5 qpidc-rdma-0.5.752581-22.el5 qpidc-ssl-0.5.752581-22.el5 qpidd-0.5.752581-22.el5 qpidd-acl-0.5.752581-22.el5 qpidd-cluster-0.5.752581-22.el5 qpidd-devel-0.5.752581-22.el5 qpid-dotnet-0.4.738274-2.el5 qpidd-rdma-0.5.752581-22.el5 qpidd-ssl-0.5.752581-22.el5 qpidd-xml-0.5.752581-22.el5 qpid-java-client-0.5.751061-7.el5 qpid-java-common-0.5.751061-7.el5 rhm-0.5.3206-5.el5 rhm-docs-0.5.756148-1.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/RHBA-2009-1153.html