activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ashwini kuntamukkala (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-4330) Removal of Master/Slave removed isSlave() JMX api
Date Tue, 13 Aug 2013 19:00:49 GMT

    [ https://issues.apache.org/jira/browse/AMQ-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738681#comment-13738681
] 

ashwini kuntamukkala commented on AMQ-4330:
-------------------------------------------

Is there anyway this can be made available in a 5.8.x release? 
                
> Removal of Master/Slave removed isSlave() JMX api
> -------------------------------------------------
>
>                 Key: AMQ-4330
>                 URL: https://issues.apache.org/jira/browse/AMQ-4330
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.8.0
>         Environment: All
>            Reporter: Matt Pavlovich
>            Assignee: Timothy Bish
>             Fix For: 5.9.0
>
>
> The task to remove the Master/Slave functionality (AMQ-4165) also removed the isSlave()
attribute from the Broker. 
> This attribute is also used when a broker is polling a shared datastore using the master+slave
polling model. Several large user groups will be impacted by this, as they have scripts that
monitor this attribute in order to re-balance brokers after maintenance or failure scenarios.
> Please reinstate.
> Thanks

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message