Return-Path: 
 <dev-return-33036-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-dev-archive@www.apache.org
Delivered-To: apmail-activemq-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 9AD1FDFFF
	for <apmail-activemq-dev-archive@www.apache.org>;
 Sat,  8 Sep 2012 18:15:08 +0000 (UTC)
Received: (qmail 88217 invoked by uid 500); 8 Sep 2012 18:15:08 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 88161 invoked by uid 500); 8 Sep 2012 18:15:07 -0000
Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@activemq.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@activemq.apache.org>
List-Post: <mailto:dev@activemq.apache.org>
List-Id: <dev.activemq.apache.org>
Reply-To: dev@activemq.apache.org
Delivered-To: mailing list dev@activemq.apache.org
Received: (qmail 88146 invoked by uid 99); 8 Sep 2012 18:15:07 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Sep 2012 18:15:07 +0000
Date: Sun, 9 Sep 2012 05:15:07 +1100 (NCT)
From: "Gaurav Sharma (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <1318552005.54419.1347128107425.JavaMail.jiratomcat@arcas>
Subject: [jira] [Created] (AMQ-4032) Failover-transport like ability for JMX
 url's
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394

Gaurav Sharma created AMQ-4032:
----------------------------------

             Summary: 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
             Fix For: 5.7.0


For the JDBC 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 user 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