You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Lahiru Gunathilake <gl...@gmail.com> on 2010/06/01 19:00:30 UTC
Re: [Java] Management CLI - Instructions
Hi Robbie,
On Sun, May 24, 2009 at 11:42 PM, Robbie Gemmell
<ro...@gmail.com>wrote:
> Confirmed, the output it gives is one of the wonderful SSL exception
> messages.
>
> It can be handled by supplying the relevant trust store for the self signed
> cert:
> export QPID_OPTS="-Djavax.net.ssl.trustStore=<path to trust store>
> -Djavax.net.ssl.trustStorePassword=<trust store password>"
>
> (use qpid/java/test_resources/ssl/certstore.jks as the trust store for the
> cert in the repository)
>
> Then you can proceed to connect in the usual fashion:
> ./qpid-cli -u <username> -w <password>
>
> These instructions doesn't work for me, I set the QPID_OPTS variables and
tried to access the broker using following command
./qpid-cli -u admin -w password
can you please tell me how to fix this.
Lahiru
> Robbie
>
> > -----Original Message-----
> > From: Robbie Gemmell [mailto:robbie.gemmell@gmail.com]
> > Sent: 22 May 2009 19:05
> > To: dev@qpid.apache.org
> > Subject: RE: [Java] Management CLI - Instructions
> >
> > 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:marnie.mccormack@googlemail.com]
> > > Sent: 22 May 2009 13:53
> > > To: dev@qpid.apache.org
> > > 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 <
> > > marnie.mccormack@googlemail.com> 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:dev-subscribe@qpid.apache.org
>
>
--
Apache Qpid, Worlds dominant messaging middleware..!!!
Senior Software Engineer
WSO2 Inc
RE: [Java] Management CLI - Instructions
Posted by Robbie Gemmell <ro...@gmail.com>.
Hi Lahiru,
I'm not really sure what to tell you, I've followed the below process on a
couple of occasions with the CLI in the last year without issue, do it all
the time with the RCP app, and its effectively what the tests do day in day
out. Perhaps the easiest course would be to just turn off the management SSL
if you don't actually plan to configure your own self-signed certificate (or
use a CA signed cert which you don't need to give a trust store for). To do
so edit the brokers etc/config.xml file and change the
<management><ssl><enabled> element value to false, then you should be able
to connect assuming the problem isn't related to something else.
Robbie
> -----Original Message-----
> From: Lahiru Gunathilake [mailto:glahiru@gmail.com]
> Sent: 01 June 2010 18:01
> To: dev@qpid.apache.org
> Subject: Re: [Java] Management CLI - Instructions
>
> Hi Robbie,
>
> On Sun, May 24, 2009 at 11:42 PM, Robbie Gemmell
> <ro...@gmail.com>wrote:
>
> > Confirmed, the output it gives is one of the wonderful SSL exception
> > messages.
> >
> > It can be handled by supplying the relevant trust store for the self
> signed
> > cert:
> > export QPID_OPTS="-Djavax.net.ssl.trustStore=<path to trust store>
> > -Djavax.net.ssl.trustStorePassword=<trust store password>"
> >
> > (use qpid/java/test_resources/ssl/certstore.jks as the trust store
> for the
> > cert in the repository)
> >
> > Then you can proceed to connect in the usual fashion:
> > ./qpid-cli -u <username> -w <password>
> >
> > These instructions doesn't work for me, I set the QPID_OPTS variables
> and
> tried to access the broker using following command
>
> ./qpid-cli -u admin -w password
>
>
> can you please tell me how to fix this.
>
> Lahiru
>
> > Robbie
> >
> > > -----Original Message-----
> > > From: Robbie Gemmell [mailto:robbie.gemmell@gmail.com]
> > > Sent: 22 May 2009 19:05
> > > To: dev@qpid.apache.org
> > > Subject: RE: [Java] Management CLI - Instructions
> > >
> > > 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:marnie.mccormack@googlemail.com]
> > > > Sent: 22 May 2009 13:53
> > > > To: dev@qpid.apache.org
> > > > 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 <
> > > > marnie.mccormack@googlemail.com> 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:dev-subscribe@qpid.apache.org
> >
> >
>
>
> --
> Apache Qpid, Worlds dominant messaging middleware..!!!
>
> Senior Software Engineer
> WSO2 Inc
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org