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: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
