[
https://issues.apache.org/jira/browse/QPID-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-2945:
---------------------------------
Affects Version/s: 0.10
0.9
Fix Version/s: (was: 0.9)
Future
> QMan 0.8RC1 is unable to connect to the 0.6 or 0.8RC1 C++ broker, and QMan
> 0.6 is unable to list resources for the 0.8RC1 C++ broker.
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-2945
> URL: https://issues.apache.org/jira/browse/QPID-2945
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker, Java Management : QMan
> Affects Versions: 0.7, 0.8, 0.9, 0.10
> Reporter: Robbie Gemmell
> Priority: Critical
> Fix For: Future
>
>
> QMan 0.7/0.8(RC1) is apparently unable to connect to the (C++) broker. QMan
> either throws an exception when trying to connect (using the MBean for the
> JMX version) or appears to do nothing and fail to connect when using the WSDM
> interface attempting to connect to the 0.8 RC1 C++ broker, continually saying
> there are no brokers connected to manage.
> When attempting to connect the 0.6 QMan to the 0.8 RC1 C++ broker, the
> connection is made and listed in the WDSM console, but no resources for the
> broker are displayed for management. When connecting the 0.6 QMan to the
> 0.6C++ broker everything appears to be fine and resources show up for
> management and can be viewed.
> From this it would seem that changes to the C++ broker since 0.6 have made
> QMan 0.6 unable to manage the 0.8 broker resources, and also that changes
> since 0.6 in the Java tree have resulted in breakage for QMan 0.8.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
