Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E5DB0200C89 for ; Sat, 20 May 2017 05:44:23 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E4A7F160BD2; Sat, 20 May 2017 03:44:23 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 379F3160BD1 for ; Sat, 20 May 2017 05:44:23 +0200 (CEST) Received: (qmail 35455 invoked by uid 500); 20 May 2017 03:44:22 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 35444 invoked by uid 99); 20 May 2017 03:44:21 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 May 2017 03:44:21 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 428911A0411 for ; Sat, 20 May 2017 03:44:21 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.414 X-Spam-Level: *** X-Spam-Status: No, score=3.414 tagged_above=-999 required=6.31 tests=[KAM_COUK=1.1, KAM_LAZY_DOMAIN_SECURITY=1, URI_HEX=1.313, URI_TRY_3LD=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id DBVFMqGEmD5z for ; Sat, 20 May 2017 03:44:20 +0000 (UTC) Received: from limey.futurelogix.co.uk (li11-11.members.linode.com [70.85.31.11]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 08AF75FC64 for ; Sat, 20 May 2017 03:44:19 +0000 (UTC) Received: from c-73-174-248-248.hsd1.pa.comcast.net ([73.174.248.248] helo=[192.168.1.130]) by limey.futurelogix.co.uk with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1dBvT8-00035u-P1 for users@activemq.apache.org; Fri, 19 May 2017 23:54:18 -0400 From: Steve Hill Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Date: Fri, 19 May 2017 23:44:07 -0400 Subject: Re: JMX url in master/slave mode Message-Id: <26254351-5C6C-43CC-8A64-E9ED3C3A4FD3@futurelogix.co.uk> References: <1495221448286-4726404.post@n4.nabble.com> In-Reply-To: <1495221448286-4726404.post@n4.nabble.com> To: users@activemq.apache.org X-Mailer: iPhone Mail (14E304) archived-at: Sat, 20 May 2017 03:44:24 -0000 I would recommend using a load balancer. You would put both up addresses in t= he load balancer. Thanks Sent from my iPhone > On May 19, 2017, at 3:17 PM, kpdude7 wrote: >=20 > How would someone programmatically access the correct JMX server in this > master/slave configuration? For example, I have the JMX url: >=20 > service:jmx:rmi:///jndi/rmi://${jmxTransferUrl}/jmxrmi >=20 > My JMS is using a failover url: > failover:(ssl://10.91.5.190:61616,ssl://10.91.5.115:61616) >=20 > What value should be substituted for ${jmxTransferUrl} above? Do I have to= > try each IP in the failover url manually and catch an exception before > trying the next one? Is there another way to do this? >=20 > Thanks, > Kyle >=20 >=20 >=20 > -- > View this message in context: http://activemq.2283324.n4.nabble.com/JMX-ur= l-in-master-slave-mode-tp4726404.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.