Description of problem: Version-Release number of selected component (if applicable): As of r4484 upstream; note that observing this requires the fix to bug 735208. How reproducible: 100% Steps to Reproduce: 1. create durable queue 2. check journal stats for that queue with qpid-tool 3. restart broker and using qpid-tool try to list journal objects Actual results: No journal stats listed on recovering broker Expected results: Journal stats available after recovery as before Additional info: See also bug 735208, whose fix is required to even see the journal stats before recovery.
This is a result on the management being initialised after the journals are created (i.e. MessageStoreImpl::initManagement() called after JournalImpl instance constructed), as a result of which the journals are given no management agent to register with.
Fixed in r.4486.
Tested using the following packages: RHEL5.7 python-qpid-0.14-1.el5 python-qpid-qmf-0.14-2.el5 qpid-cpp-client-0.14-3.el5 qpid-cpp-client-devel-0.14-3.el5 qpid-cpp-client-devel-docs-0.14-3.el5 qpid-cpp-client-rdma-0.14-3.el5 qpid-cpp-client-ssl-0.14-3.el5 qpid-cpp-debuginfo-0.12-6.el5 qpid-cpp-server-0.14-3.el5 qpid-cpp-server-cluster-0.14-3.el5 qpid-cpp-server-devel-0.14-3.el5 qpid-cpp-server-rdma-0.14-3.el5 qpid-cpp-server-ssl-0.14-3.el5 qpid-cpp-server-store-0.14-3.el5 qpid-java-client-0.14-1.el5 qpid-java-common-0.14-1.el5 qpid-java-example-0.14-1.el5 qpid-qmf-0.14-2.el5 qpid-qmf-debuginfo-0.14-2.el5 qpid-qmf-devel-0.14-2.el5 qpid-tools-0.14-1.el5 RHEL6.2 python-qpid-0.14-1.el6 python-qpid-qmf-0.14-3.el6 qpid-cpp-client-0.14-1.el6 qpid-cpp-client-devel-0.14-1.el6 qpid-cpp-client-devel-docs-0.14-1.el6 qpid-cpp-client-rdma-0.14-1.el6 qpid-cpp-client-ssl-0.14-1.el6 qpid-cpp-debuginfo-0.14-1.el6 qpid-cpp-server-0.14-1.el6 qpid-cpp-server-cluster-0.14-1.el6 qpid-cpp-server-devel-0.14-1.el6 qpid-cpp-server-rdma-0.14-1.el6 qpid-cpp-server-ssl-0.14-1.el6 qpid-cpp-server-store-0.14-1.el6 qpid-cpp-server-xml-0.14-1.el6 qpid-qmf-0.14-3.el6 qpid-qmf-devel-0.14-3.el6 qpid-tools-0.14-1.el6 -> VERIFIED
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: Recovery of an existing durable queue (as opposed to creating a new one) would not return management stats. Consequence: It was not possible to monitor the status of any recovered persistent queue. Result: After the fix, the management statistics are correctly initialized and may be queried in the same way as newly created queues.
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-2012-0529.html