activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-984) make the "slave" status of a broker available through JMX (in jdbc-master-slave mode)
Date Tue, 09 Sep 2008 10:07:52 GMT

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

Gary Tully resolved AMQ-984.
----------------------------

      Assignee: Gary Tully
    Resolution: Fixed

isSlave brokerMbean attribute added in r693414. Becomes true while slave is waiting to acquire
shared lock. False otherwise. It is false for master.

> 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
>            Assignee: Gary Tully
>            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.


Mime
View raw message