[
https://issues.apache.org/activemq/browse/AMQ-984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45544#action_45544
]
Gary Tully commented on AMQ-984:
--------------------------------
a few years later but BrokerService has an isSlave() method, Explosing that
readonly attribute would give the same information I guess. It will only be
true while waiting for the lock, when the lock is acquired it will be false.
Would this suffice?
> make the "slave" status of a broker available through JMX (in
> jdbc-master-slave mode)
> -------------------------------------------------------------------------------------
>
> Key: AMQ-984
> URL: https://issues.apache.org/activemq/browse/AMQ-984
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 4.1.0
> Reporter: Renaud Bruyeron
> Priority: Minor
> Fix For: 5.3.0
>
>
> Right now, it is not possible to know that a broker is in "Attempting to
> acquire the exclusive lock to become the Master broker" mode via JMX, even
> though this would be a natural place to find out.
> Do you think it would be possible to expose the DatabaseLocker or the
> JDBCPersistenceAdapter over JMX so that a simple boolean isMaster() can be
> queried?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
