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 B0CA7200C72 for ; Fri, 12 May 2017 18:00:47 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id AF348160BA3; Fri, 12 May 2017 16:00:47 +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 80726160BB8 for ; Fri, 12 May 2017 18:00:46 +0200 (CEST) Received: (qmail 1268 invoked by uid 500); 12 May 2017 16:00:45 -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 862 invoked by uid 99); 12 May 2017 16:00:45 -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 16:00:45 +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 E2A2A1A7A6E for ; Fri, 12 May 2017 16:00:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.315 X-Spam-Level: ** X-Spam-Status: No, score=2.315 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_NONE=-0.0001, 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 bJcDKLow94WH for ; Fri, 12 May 2017 16:00:41 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 313045FC3D for ; Fri, 12 May 2017 16:00:41 +0000 (UTC) Received: from mjoe.nabble.com (unknown [162.253.133.57]) by mwork.nabble.com (Postfix) with ESMTP id E4149411281D9 for ; Fri, 12 May 2017 09:00:39 -0700 (MST) Date: Fri, 12 May 2017 08:47:55 -0700 (PDT) From: mtod To: users@activemq.apache.org Message-ID: <1494604075989-4726064.post@n4.nabble.com> In-Reply-To: <1284146734.8305626.1494604020475.JavaMail.zimbra@redhat.com> References: <1494535459294-4726002.post@n4.nabble.com> <1284146734.8305626.1494604020475.JavaMail.zimbra@redhat.com> Subject: Re: Artemis 2.0 cluster fail over issue MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Fri, 12 May 2017 16:00:47 -0000 Thanks for the response. 3 systems running on AWS Windows 2016 I just trimed it down removing any SSL until I can get this working. I followed the https://github.com/apache/activemq-artemis/tree/master/examples/features/ha/replicated-transaction-failover example. Quick question how does the cluster know when a master fails is the a ping if so what port does that use? Thanks for looking at this. Mike Server1 - Master fmibroker true true NIO ./data/paging ./data/bindings ./data/journal ./data/large-messages true 2 -1 1488000 tcp://10.121.51.121:61616 5000 90 100Mb tcp://10.121.51.121:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENWIRE xxxxx xxxxx ${udp-address:231.7.7.7} 9876 5000 netty_connector ${udp-address:231.7.7.7} 9876 10000 netty_connector 1000 ON_DEMAND 1 fmieastcluster useast true jms.queue.activemq.management DLQ ExpiryQueue 0 -1 10 PAGE true true true true DLQ ExpiryQueue 0 -1 10 PAGE true true true true
Server2 - Slave fmibroker true true NIO ./data/paging ./data/bindings ./data/journal ./data/large-messages true 2 -1 1364000 tcp://10.121.49.225:61616 5000 90 100Mb tcp://10.121.49.225:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENWIRE xxxxx xxxxx ${udp-address:231.7.7.7} 9876 5000 netty_connector ${udp-address:231.7.7.7} 9876 10000 netty_connector 1000 ON_DEMAND 1 fmieastcluster useast true DLQ ExpiryQueue 0 -1 10 PAGE true true true true DLQ ExpiryQueue 0 -1 10 PAGE true true true true
Server3 - Slave fmibroker true true NIO ./data/paging ./data/bindings ./data/journal ./data/large-messages true 2 -1 1488000 tcp://10.121.44.48:61616 5000 90 100Mb tcp://10.121.44.48:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENWIRE xxxxx xxxxx ${udp-address:231.7.7.7} 9876 5000 netty_connector ${udp-address:231.7.7.7} 9876 10000 netty_connector 1000 ON_DEMAND 1 fmieastcluster useast true jms.queue.activemq.management DLQ ExpiryQueue 0 -1 10 PAGE true true true true DLQ ExpiryQueue 0 -1 10 PAGE true true true true
-- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-2-0-cluster-fail-over-issue-tp4726002p4726064.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.