[
https://issues.apache.org/jira/browse/QPID-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931865#action_12931865
]
Robbie Gemmell edited comment on QPID-2945 at 11/14/10 2:14 PM:
----------------------------------------------------------------
Part of the issue seems to be that Mina is missing from the 0.8RC1 QMan archive
but was included in the 0.6 QMan release archive. This difference is seemingly
due to a change made to the build system in *April*, such that the build.deps
file entries only lists the dependencies of a module itself, and not also the
dependencies of those other modules it depends on; those jars are now pulled
into the 'ant release-bin' packages using the 'depends' definition in the
module build file. However, the QMan build file overrides the standard
release-bin targets and does much of the work itself, and so requires
dependencies-of-dependcies still be specified in build.deps. Regardless, the
fact that the 0.6 QMan release (from which there has been no intended change to
QMan) still doesnt seem able to work with the 0.8RC1 C++ broker suggests there
are larger issues to look it. As such, per QPID-2946, I have removed the QMan
convencience archive from the (0.8) release process.
was (Author: gemmellr):
Part of the issue seems to be that Mina is missing from the 0.8RC1 QMan
archive but was included in the 0.6 QMan release archive. This difference is
seemingly due to a change made to the build system in *April*, such that the
build.deps file entries only lists the dependencies of a module itself, and not
also the dependencies of those other modules it depends on; those jars are now
pulled into the 'ant release-bin' packages using the 'depends' definition in
the module build file. However, the QMan build file overrides the standard
release-bin targets and does much of the work itself, and so requires
dependencies-of-dependcies still be specified in build.deps. Regardless, the
fact that the 0.6 QMan release (from which there has been no intended change to
QMan) still doesnt seem able to work with the 0.8RC1 C++ broker suggests there
are larger issues to look it. As such, per QPID-2945, I have removed the QMan
convencience archive from the (0.8) release process.
> 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.8, 0.7
> Reporter: Robbie Gemmell
> Priority: Critical
> Fix For: 0.9
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
