Description of problem: If an acquired message is released, it is requeued in such a way that subsequent browsing of the queue is affected. This is a result of it being requeued in the wrong position in the queue. Version-Release number of selected component (if applicable): qpidd-0.5.752581-30.el5 How reproducible: 100% Steps to Reproduce: (using attached example programs) 1. for m in aaa bbb ccc; do echo $m; done | ./send 2. ./example3 3. don't process aaa, do process bbb, don't process ccc; then ctrl-c to exit 4. restart: ./example3 Actual results: Only see ccc until that is consumed Expected results: Should see both aaa and ccc. Additional info:
Created attachment 367813 [details] acquiring client
Created attachment 367814 [details] sending client
Fixed on trunk by r834026.
Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Resolved problem with incorrect positioning of the requeued messages resulting from release of the acquired messages: releases messages no longer hamper message queue browsing.
The issue has been fixed, verified on RHEL 4.8 / 5.4 i386 / x86_64 on packages: [root@mrg-qe-01 bz533361]# rpm -qa | egrep '(rhm|qpid|qmf)' | sort -u condor-qmf-plugins-7.4.1-0.5.el5 python-qpid-0.5.752581-4.el5 qmf-0.5.752581-34.el5 qmf-devel-0.5.752581-34.el5 qpidc-0.5.752581-34.el5 qpidc-debuginfo-0.5.752581-31.el5 qpidc-devel-0.5.752581-34.el5 qpidc-perftest-0.5.752581-34.el5 qpidc-rdma-0.5.752581-34.el5 qpidc-ssl-0.5.752581-34.el5 qpidd-0.5.752581-34.el5 qpidd-acl-0.5.752581-34.el5 qpidd-cluster-0.5.752581-34.el5 qpidd-devel-0.5.752581-34.el5 qpid-dotnet-0.4.738274-2.el5 qpidd-rdma-0.5.752581-34.el5 qpidd-ssl-0.5.752581-34.el5 qpidd-xml-0.5.752581-34.el5 qpid-java-client-0.5.751061-9.el5 qpid-java-common-0.5.751061-9.el5 rhm-0.5.3206-27.el5 rhm-debuginfo-0.5.3206-16.el5 rhm-docs-0.5.756148-1.el5 -> VERIFIED
Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1,8 @@ -Resolved problem with incorrect positioning of the requeued messages resulting from release of the acquired messages: releases messages no longer hamper message queue browsing.+Messaging bug fix + +C: Dequeued messages were being requeued in the wrong order. +C: When the queue was browsed, messages did not appear as expected +F: Requeuing of messages now occurs in the correct order +R: Browsing a queue with requeued messages is accurate. + +Dequeued messages were being requeued in the wrong order, resulting in messages not appearing correctly when the queue was browsed. Requeuing of messages now occurs in the correct order and browsing a queue with requeued messages is accurate.
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-2009-1633.html