activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-984) make the "slave" status of a broker available through JMX (in jdbc-master-slave mode)
Date Mon, 13 Nov 2006 21:43:04 GMT
     [ https://issues.apache.org/activemq/browse/AMQ-984?page=all ]

Hiram Chirino updated AMQ-984:
------------------------------

    Fix Version/s: 4.2
                       (was: 4.1.0)

> 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: 4.2.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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message