Description of problem: The alternate exchange attribute of a queue is not accessible via QMF. Version-Release number of selected component (if applicable): 1.1.6 / 1.2 How reproducible: 100% Steps to Reproduce: 1. qpid-config add queue queue-name --alternate-exchange amq.fanout 2. qpid-config queues 3. View the queue using qpid-tool Actual results: The alternate exchange is not visible in either qpid-config or in qpid-tool. The queue does have an alternate exchange and behaves correctly, it is simply invisible through QMF. Expected results: Expect to see "amq.fanout" in both tools. Additional info: Note that this is a model deficiency. The QMF schema for broker queues does not have an altExchange property. Once this is fixed, qpid-config will need to be updated to recognize and display this attribute.
There is actually a altExchange property in the schema, it just wasn't tagged as a reference. I fixed that on 9/15, at svn rev 815449 (see below). But qpid-config may still need to be updated. Author: nsantos Date: Tue Sep 15 19:00:05 2009 New Revision: 815449 URL: http://svn.apache.org/viewvc?rev=815449&view=rev Log: add missing 'references' attrib to altExchange Modified: qpid/trunk/qpid/specs/management-schema.xml Modified: qpid/trunk/qpid/specs/management-schema.xml URL: http://svn.apache.org/viewvc/qpid/trunk/qpid/specs/management-schema.xml?rev=815449&r1=815448&r2=815449&view=diff ============================================================================== --- qpid/trunk/qpid/specs/management-schema.xml (original) +++ qpid/trunk/qpid/specs/management-schema.xml Tue Sep 15 19:00:05 2009 @@ -169,7 +169,7 @@ <property name="type" type="sstr" access="RO"/> <property name="durable" type="bool" access="RO"/> <property name="autoDelete" type="bool" access="RO"/> - <property name="altExchange" type="objId" access="RO" optional="y"/> + <property name="altExchange" type="objId" references="Exchange" access="RO" optional="y"/> <property name="arguments" type="map" access="RO" desc="Arguments supplied in exchange.declare"/> <statistic name="producerCount" type="hilo32" desc="Current producers on exchange"/>
The update in revision 815449 affects the "exchange" class. This bug is about the "queue" class which needs an altExchange property but doesn't have one. -Ted
*** Bug 531921 has been marked as a duplicate of this bug. ***
Fixed upstream at revision 831351.
This is not visible on 1.2 as --alternate-exchange does not exist in qpid-config 1.2. Newer version have to be used to reproduce this. fixed on qpid-tools-0.7.946106-10 alternate exchange shown. validated on RHEL5.5/RHEL4 i386 / x86_64 packages: # rpm -qa | grep -E '(qpid|openais|rhm)' | sort -u openais-0.80.6-16.el5_5.7 openais-devel-0.80.6-16.el5_5.7 python-qpid-0.7.946106-14.el5 qpid-cpp-client-0.7.946106-15.el5 qpid-cpp-client-devel-0.7.946106-15.el5 qpid-cpp-client-devel-docs-0.7.946106-15.el5 qpid-cpp-client-ssl-0.7.946106-15.el5 qpid-cpp-mrg-debuginfo-0.7.946106-14.el5 qpid-cpp-server-0.7.946106-15.el5 qpid-cpp-server-cluster-0.7.946106-15.el5 qpid-cpp-server-devel-0.7.946106-15.el5 qpid-cpp-server-ssl-0.7.946106-15.el5 qpid-cpp-server-store-0.7.946106-15.el5 qpid-cpp-server-xml-0.7.946106-15.el5 qpid-java-client-0.7.946106-9.el5 qpid-java-common-0.7.946106-9.el5 qpid-tools-0.7.946106-10.el5 rhm-docs-0.7.946106-5.el5 rh-tests-distribution-MRG-Messaging-qpid_common-1.6-53 ->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: Previously, the alternate exchange attribute of a queue was not accessible via QMF. The alternate exchange was not visible in either qpid-config or in qpid-tool. The queue did have an alternate exchange and behaved correctly, however it was simply invisible through QMF. With this update, the queue is accessible via QMF as expected.
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/RHSA-2010-0773.html