Details
-
Bug
-
Resolution: Done
-
Major
-
JBoss A-MQ 6.1
-
None
Description
When configuring a broker pair using a shared file system master/slave configuration, it the slave broker is configured with the scheduler enable:
<broker xmlns="http://activemq.apache.org/schema/core" brokerName="localhost" dataDirectory="${activemq.data}" schedulerSupport="true">
The slave broker does not register it's mBean information vis JMX. From looking at the log of the slave broker the following can be seen:
INFO | Database /Users/jsherman/Development/tools/jboss-amq/apache-activemq-5.9.0.redhat-610379/data/localhost/scheduler/lock is locked... waiting 10 seconds for the database to be unlocked. Reason: java.io.IOException: File '/Users/jsherman/Development/tools/jboss-amq/apache-activemq-5.9.0.redhat-610379/data/localhost/scheduler/lock' could not be locked.
In this case it appears the broker is stuck trying to lock the scheduler lock file before the mBean can be registered.
Without the scheduler enable, the mBean is registered in JMX and log shows the broker is just waiting to locl the kahadb lock file:
INFO | Database /Users/jsherman/Development/tools/jboss-amq/apache-activemq-5.9.0.redhat-610379/data/kahadb/lock is locked... waiting 5 seconds for the database to be unlocked. Reason: java.io.IOException: File '/Users/jsherman/Development/tools/jboss-amq/apache-activemq-5.9.0.redhat-610379/data/kahadb/lock' could not be locked.
