The below looks reasonable, in which case another option would be that the mbean provider isnt being discovered. Do you have the qpid-bdbstore-jmx jar in your lib/plugins folder?
If so, can you outline the steps you used to set up and start the broker? I downloaded the 0.20 release before replying earlier and tried this out without incident, simply adding the BDB JE jar and configuring a vhost with the HA store using the example from the 0.20 docs (sans typo), after which starting the broker I found the MBean has been created. Robbie On 1 August 2013 16:11, jbelch <[email protected]> wrote: > My active node's configuration looks like the following: > > <virtualhost> > <name>test</name> > <test> > <store> > > <class>org.apache.qpid.server.store.berkeleydb.BDBHAMessageStore</class> > > <environment-path>${QPID_WORK}/bdbhastore/eutilrhs1</environment-path> > <highAvailability> > <groupName>ReplicationGroup</groupName> > <nodeName>eutilrhs1</nodeName> > <nodeHostPort>eutilrhs1:5001</nodeHostPort> > <helperHostPort>eutilrhs1:5001</helperHostPort> > <durability>SYNC\,SYNC\,SIMPLE_MAJORITY</durability> > <coalescingSync>false</coalescingSync> > <designatedPrimary>true</designatedPrimary> > </highAvailability> > </store> > .... > </test> > <virtualhost> > > I know it working because I have a couple of queues setup as durable. I > publish durable messages to those queues, cycle the broker, and the message > persist. I can also see the messages being written to the bdbhastore > directory. I added -DJEMonitor=true to the qpid-server script and now I > have a "com.sleepycat.je.jmx" element in the jconsole tree, but I still > don't have the BDBHAMessageStore element. > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/JMX-interface-with-Java-Broker-20-tp7596278p7596312.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
