Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 760112 - Journal management stats not available for recovered queues
Journal management stats not available for recovered queues
Status: CLOSED ERRATA
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp (Show other bugs)
Development
Unspecified Unspecified
medium Severity medium
: 2.1.2
: ---
Assigned To: Kim van der Riet
Leonid Zhaldybin
:
Depends On:
Blocks: 783492
  Show dependency treegraph
 
Reported: 2011-12-05 08:23 EST by Gordon Sim
Modified: 2014-11-09 17:38 EST (History)
3 users (show)

See Also:
Fixed In Version: qpid-cpp-mrg-0.14-3.el5
Doc Type: Bug Fix
Doc Text:
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.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-04-30 13:53:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:0529 normal SHIPPED_LIVE Moderate: Red Hat Enterprise MRG Messaging 2.1 security and enhancement update 2012-04-30 17:48:25 EDT

  None (edit)
Description Gordon Sim 2011-12-05 08:23:04 EST
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.
Comment 1 Gordon Sim 2011-12-05 08:27:38 EST
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.
Comment 2 Kim van der Riet 2011-12-08 16:59:33 EST
Fixed in r.4486.
Comment 4 Leonid Zhaldybin 2012-01-12 04:34:40 EST
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
Comment 5 Kim van der Riet 2012-03-09 12:54:21 EST
    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.
Comment 6 errata-xmlrpc 2012-04-30 13:53:18 EDT
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

Note You need to log in before you can comment on or make changes to this bug.