[jira] [Resolved] (AMQ-5746) Slave broker not registering JMX mBean when scheduler is enabled

["Gary Tully (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-5746.
-----------------------------
    Resolution: Fixed

fix and test in http://git-wip-us.apache.org/repos/asf/activemq/commit/c1290511

scheduler store needs to be started after mbean registration

> Slave broker not registering JMX mBean when scheduler is enabled
> ----------------------------------------------------------------
>
>                 Key: AMQ-5746
>                 URL: https://issues.apache.org/jira/browse/AMQ-5746
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, Job Scheduler
>    Affects Versions: 5.11.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.12.0
>
>
> {code}
> <broker xmlns="http://activemq.apache.org/schema/core" brokerName="localhost" dataDirectory="${activemq.data}" schedulerSupport="true">
> {code}
> 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:
> {code}
> 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.
> {code}
> 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:
> {code}
> 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.
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)