I haven't tested it (yet), but the CLI is using the same JMX connection classes as the RCP app does (shared in management-common) so it should be ok, meaning any problem is probably related to the defaulted-on use of SSL on the brokers JMX server.
If the broker is using a self signed ssl cert, the CLI will need supplied the same environment properties as the RCP based MC does, to indicate a matching ssl trust store. If a CA signed ssl cert is being used and the relevant CA is included within the default java trust store it shouldn't need told anything. Robbie, (who is now entering hibernation following a week of next to no sleep :P) > -----Original Message----- > From: Marnie McCormack [mailto:[email protected]] > Sent: 22 May 2009 13:53 > To: [email protected] > Subject: Re: [Java] Management CLI - Instructions > > Hi, > > Just been trying out the CLI and I *think* it no longer connects out of > the > box since the authentication on management connnections was enforced. > > Anyone able to correct/confirm ? > > Marnie > > On Fri, May 22, 2009 at 12:17 PM, Marnie McCormack < > [email protected]> wrote: > > > Hi Lahiru, > > > > Been using the CLI and wondered if it might be possible to get the > detailed > > instructions from your blog ( > > http://lahirumanaya.blogspot.com/2008/08/what-qpid-management- > console-can-do.html) > > added into the readme or the Qpid web page ( > > http://qpid.apache.org/qpid-java-broker-management-cli.html) ? > > > > If they're still up-to-date, I'm happy to bring them over if that'd > be ok ? > > > > > > The instructions on the blog are really what users need, i think, so > would > > be great to ship them with our next release. > > > > What do you think ? > > > > Thanks & Regards, > > Marnie > > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
