Bug 760112
| Summary: | Journal management stats not available for recovered queues | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Gordon Sim <gsim> |
| Component: | qpid-cpp | Assignee: | Kim van der Riet <kim.vdriet> |
| Status: | CLOSED ERRATA | QA Contact: | Leonid Zhaldybin <lzhaldyb> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | Development | CC: | esammons, jross, lzhaldyb |
| Target Milestone: | 2.1.2 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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 17:53:18 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 783492 | ||
|
Description
Gordon Sim
2011-12-05 13:23:04 UTC
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 |