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 4B7E8200C72 for ; Fri, 12 May 2017 21:23:45 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 49DA1160BB8; Fri, 12 May 2017 19:23:45 +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 90B44160BA8 for ; Fri, 12 May 2017 21:23:44 +0200 (CEST) Received: (qmail 64873 invoked by uid 500); 12 May 2017 19:23:43 -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 64858 invoked by uid 99); 12 May 2017 19:23:43 -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; Fri, 12 May 2017 19:23:43 +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 DF5C81A0050 for ; Fri, 12 May 2017 19:23:42 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -3.707 X-Spam-Level: X-Spam-Status: No, score=-3.707 tagged_above=-999 required=6.31 tests=[HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_TRY_3LD=0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id gYRZSPw5FDin for ; Fri, 12 May 2017 19:23:41 +0000 (UTC) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 77F285F5C4 for ; Fri, 12 May 2017 19:23:40 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 4C0A5C04B94A for ; Fri, 12 May 2017 19:23:39 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 4C0A5C04B94A Authentication-Results: ext-mx07.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=apache.org Authentication-Results: ext-mx07.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=jbertram@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 4C0A5C04B94A Received: from colo-mx.corp.redhat.com (colo-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 40CB25C6E3 for ; Fri, 12 May 2017 19:23:39 +0000 (UTC) Received: from zmail22.collab.prod.int.phx2.redhat.com (zmail22.collab.prod.int.phx2.redhat.com [10.5.83.26]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id 09BD7180886C for ; Fri, 12 May 2017 19:23:39 +0000 (UTC) Date: Fri, 12 May 2017 15:23:38 -0400 (EDT) From: Justin Bertram To: users@activemq.apache.org Message-ID: <933296172.8364029.1494617018954.JavaMail.zimbra@redhat.com> In-Reply-To: <1494615431915-4726089.post@n4.nabble.com> References: <1474383223.8311142.1494605681599.JavaMail.zimbra@redhat.com> <1494607641448-4726076.post@n4.nabble.com> <513255241.8333357.1494610577194.JavaMail.zimbra@redhat.com> <1494610464026-4726081.post@n4.nabble.com> <1537554558.8339897.1494612112778.JavaMail.zimbra@redhat.com> <1494612259406-4726084.post@n4.nabble.com> <920210086.8354867.1494614500079.JavaMail.zimbra@redhat.com> <1494615431915-4726089.post@n4.nabble.com> Subject: Re: Artemis 2.0 cluster fail over issue MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.10.123.226, 10.4.195.3] Thread-Topic: Artemis 2.0 cluster fail over issue Thread-Index: eL+EHEnOWbw6/NuyTJUAjQBK7IEqRQ== X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Fri, 12 May 2017 19:23:39 +0000 (UTC) archived-at: Fri, 12 May 2017 19:23:45 -0000 I believe discovery is still possible using JGroups (e.g. using S3_PING [1] or AWS_PING [2]). Justin [1] http://jgroups.org/manual/index.html#_s3_ping [2] http://jgroups.org/manual/index.html#_aws_ping ----- Original Message ----- From: "mtod" To: users@activemq.apache.org Sent: Friday, May 12, 2017 1:57:11 PM Subject: Re: Artemis 2.0 cluster fail over issue Just to close this out I setup static connections and it's failing over fine. I would have preferred to use the discovery but seems that's not possible at this time on AWS. Thanks for your help Mike -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-2-0-cluster-fail-over-issue-tp4726002p4726089.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.