Thank You ! Lahiru
On Thu, Jun 25, 2009 at 10:39 PM, Robbie Gemmell <[email protected]>wrote: > > SSL is enabled by default on the JMX connection, which affects remote > connections. There are instructions on the website for setting jconsole up > accordingly, or you can turn the ssl off in etc/config.xml > > However, if you launch the broker and jconsole on the same machine you can > connect directly to the broker process (instead of specifying > localhost:8999) using jconsole and bypass the issue entirely. I am working > on some jmx stuff just now so I know it definitely still works. > > Make sure the username you are using has permissions in the > etc/jmxremote.access file as well as a password in the etc/passwd file or > you will be denied acces. > > To connect with your CLI with SSL enabled, provide the required SSL > properties (decsribed on website) via the QPID_OPTS env variable, as I > described in an email recently (that you replied to). > > Sorry I can't give URLs just now, I'm stuck using my phone. > > > On 25 Jun 2009, at 17:09, Lahiru Gunathilake <[email protected]> wrote: > > Hi Devs, >> >> I tried to connect to Qpid Java broker using Jconsole but couldn't connect >> in one shot. Tried to do several things but couldn't connect in the >> latest >> svn build. Is there any special configuration required to connect Java >> broker. >> 1. Tried to connect to the local process (failed) >> 2. Tried to connect remotely using JMX port which is by default 8999. >> >> Thanks >> Lahiru >> >> -- >> Apache Qpid, Worlds dominant messaging middleware..!!! >> > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > -- Apache Qpid, Worlds dominant messaging middleware..!!!
