[
https://issues.apache.org/jira/browse/AMQ-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574099#comment-13574099
]
Rob Waite commented on AMQ-4032:
--------------------------------
I maybe misunderstand... but it seems to me that JMX connections through the
RemoteJMXBrokerFacade already supports failover..
{code}
String jmxUri = properties.getProperty("jmxUri");
Properties p = System.getProperties();
p.setProperty("webconsole.jmx.url", jmxUri);
brokerProxy = new RemoteJMXBrokerFacade();
SystemPropertiesConfiguration spc = new SystemPropertiesConfiguration();
brokerProxy.setConfiguration(spc);
{code}
I am able to failover back and forth between nodes and the
RemoteJMXBrokerFacade connects to the other node on the next call.
Is there something I am missing?
> Failover-transport like ability for JMX url's
> ---------------------------------------------
>
> Key: AMQ-4032
> URL: https://issues.apache.org/jira/browse/AMQ-4032
> Project: ActiveMQ
> Issue Type: Improvement
> Components: JMX
> Affects Versions: 5.6.0
> Reporter: Gaurav Sharma
> Labels: patch
> Fix For: 5.x
>
> Attachments: AMQ-4032_roughPatch.txt
>
>
> For the Master Slave config, just like there exists the Failover
> Transport for the broker url, support specification of the JMX
> hosts via configuration:
> jmxUrl=service:jmx:rmi:///jndi/rmi://<host1>:1616/jmxrmi,
> service:jmx:rmi:///jndi/rmi://<host2>:1616/jmxrmi,
> service:jmx:rmi:///jndi/rmi://<host3>:1616/jmxrmi
> so that users do not have to worry about managing 3 MBeanServerConnection's
> in code and then trying to figure which one is the master or which
> one is alive, worry about re-election, etc.
--
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
