qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell" <robbie.gemm...@gmail.com>
Subject RE: QMan JMX / 0.6 RC3 issue
Date Mon, 11 Jan 2010 22:05:45 GMT
Ok, got it all working ;)

As I mentioned below I could see the QMan service MBean, I just couldn't
seem to get it to do anything else. What I forgot to mention was that I was
getting an UnmarshallingException when trying to use the addBroker() method
with of the MBean with the same example configuration info that appears to
work fine using the wsdm startup script (from etc/qman-config.xml). 

However I just took a dig around the broker using qpid-tool (also first time
using that hehe) and realised I should be using virtualhost '/' instead of
the example 'test', and now it works: The addBroker() method returns
succesfully and I can see the MBeans for the managed objects on the broker,
and see the management queues created by QMan in qpid-tool

So, confirmed it works, but perhaps the example config should be updated. I
also find it strange the WSDM QMan manages to connect on startup to the
broker and generate MBeans when using the example configuration with the
incorrect 'test' virtualhost and the JMX startup doesn't, but the docs say
it should (it doesn't seem to auto connect when the vhost is changed to '/'
either). Also the URL for the web admin in the README appears to be wrong, I
had to go to http://<host>:<port>/qman/console to get it rather than the
noted http://<host>:<port>/qman/admin.jsp


> -----Original Message-----
> From: Andrea Gazzarini [mailto:a.gazzarini@gmail.com]
> Sent: 11 January 2010 21:15
> To: dev@qpid.apache.org
> Subject: Re: QMan JMX / 0.6 RC3 issue
> Hi Robbie,
> I can try to give you a help...
> - Do you see in JConsole a QMan MBean (or something like that I don't
> remember exactly the name)? It should have a connect() method that you
> can
> use to connect to a new broker.
> - Could you please try to set to DEBUG and send me the qman.log file?
> Regards,
> Andrea
> 2010/1/11 Robbie Gemmell <robbie.gemmell@quasareclipse.co.uk>
> > Hey all,
> >
> > I was just trying out the QMan bundle from 0.6 RC3, and I'm having
> some
> > problems getting the standalone JMX side of it to do much of
> anything.
> >
> > If I edit the etc/qman-config.xml file to uncomment the broker
> config,
> > start
> > QMan using the qman-wsdm-start.sh script, and then connect JConsole
> to the
> > QMan process I can see the QMan Service MBean plus MBeans
> representing the
> > queues etc. I can see the management queues it created on the C++
> broker
> > using qpid-tool, and the QMan web management console starts up and I
> can
> > browse it (although it's not at the exact address noted in the
> > documentation).
> >
> > If I start QMan using the bin/qman-jmx.sh script it starts up, I get
> the
> > expected 'press q to quit' message, the QMan Ser
> > vice MBean is shown if I
> > connect using JConsole, but beyond that it doesn't seem to want to do
> > anything. No additional MBeans to represent the managed objects, no
> > management queues visible in qpid-tool. I downloaded the 0.5 bundle
> and it
> > seems much the same [tested with the 0.6 RC3 broker, that is].
> >
> > I haven't used QMan at all before so I'm possibly just missing a
> step, but
> > as far as I can see I'm doing what the docs say. Anyone got any
> experience
> > using it? Rajith, I see you have modified the JMX startup script at
> various
> > points, any tips?
> >
> > Robbie
> >
> >
> > ---------------------------------------------------------------------
> > Apache Qpid - AMQP Messaging Implementation
> > Project:      http://qpid.apache.org
> > Use/Interact: mailto:dev-subscribe@qpid.apache.org
> >
> >

Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org

View raw message