Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
5.11.0
-
None
Description
<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 /scheduler/lock is locked... waiting 10 seconds for the database to be unlocked. Reason: java.io.IOException: File '/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 lock the kahadb lock file:
INFO | Database kahadb/lock is locked... waiting 5 seconds for the database to be unlocked. Reason: java.io.IOException: File 'kahadb/lock' could not be locked.