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 97D1F200B27 for ; Wed, 22 Jun 2016 11:24:18 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 9670D160A35; Wed, 22 Jun 2016 09:24:18 +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 DE00C160A2E for ; Wed, 22 Jun 2016 11:24:17 +0200 (CEST) Received: (qmail 79212 invoked by uid 500); 22 Jun 2016 09:24:17 -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 79201 invoked by uid 99); 22 Jun 2016 09:24:16 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Jun 2016 09:24:16 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 3EDD4C0DF4 for ; Wed, 22 Jun 2016 09:24:16 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.675 X-Spam-Level: ** X-Spam-Status: No, score=2.675 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URI_HEX=1.313, URI_TRY_3LD=0.064] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id fGVJKg9oLupU for ; Wed, 22 Jun 2016 09:24:13 +0000 (UTC) Received: from mail-io0-f179.google.com (mail-io0-f179.google.com [209.85.223.179]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 598B45F571 for ; Wed, 22 Jun 2016 09:24:13 +0000 (UTC) Received: by mail-io0-f179.google.com with SMTP id t74so38985866ioi.0 for ; Wed, 22 Jun 2016 02:24:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=xl+4Qqy3Ty37Mh7CCYASOSs4u5rq175DnNu9zPvneyw=; b=M+6Lcn5+8n3+KntW6G8RmW90UNgjm/s8CbAtklLDd6bldhXvRJDO/2IdFl/2UCYDgu FWWSs4EXmM4me5a6dyL0DYTydaUKpvHES50WPDwVeXHDK8JEZF7wSPkXR5JW/kBYnxzU Qv2Wr1UIfOKqyK2ej3U8G4m6lF6E0WxZ/wT21Nh/2sZZOstkwn0tU7olJ9SMT4bZ2XZG L21jqwbyx/sY3rLwuxdBQRG4NsVydfFnRLv+EJ8UdbsuR0EUGDzTIcISa1tkMkg+sBFI tipUxu9y1LQAOi79P1r81hJyy5CVEPDL6o5ZJeP+kheTLMWcuCsfPnAdbjzTVthF57lK XPUg== X-Gm-Message-State: ALyK8tKagFI7ZuSV9TlsY4Lt6UxDdJpdOpOA5okt7LnKoS6p/VxNDgRVNZ5OE63utzhGa/GttytFXYkt19PqdJrj X-Received: by 10.107.140.148 with SMTP id o142mr3647173iod.42.1466587452492; Wed, 22 Jun 2016 02:24:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.7.23 with HTTP; Wed, 22 Jun 2016 02:24:11 -0700 (PDT) In-Reply-To: <1466576312196-4713231.post@n4.nabble.com> References: <1466510483960-4713190.post@n4.nabble.com> <1466519025941-4713197.post@n4.nabble.com> <1466576312196-4713231.post@n4.nabble.com> From: Martyn Taylor Date: Wed, 22 Jun 2016 10:24:11 +0100 Message-ID: Subject: Re: Artemis: Automatic failback does not work To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=94eb2c0717a223655c0535da808b archived-at: Wed, 22 Jun 2016 09:24:18 -0000 --94eb2c0717a223655c0535da808b Content-Type: text/plain; charset=UTF-8 Hi Sebastian, Good to hear this resolved your problem. The whole connector/acceptor concept in Artemis is a little bit confusing. In short, the acceptor in the config is a way to configure the broker to allow clients to connect. It opens a port, configures the protocols etc.... A Connector is essentially information that is passed to the clients (or other brokers) instructing them how to connect to the broker. It get's broadcast to other nodes (providing broadcast is configured), This allows cluster nodes to discover each other, they take the connector information then use it to connect to an acceptor on another node. In your case, you had the connector/acceptor configured properly on the master node, so the slave was able to discover and connector to it. But when failback happened the master node was unable to connect to the slave (current live) since the connector information was wrong. There's a section on transports in the user manual that covers acceptors and connectors, it's worth a read because the acceptor/connector stuff is not obvious. https://activemq.apache.org/artemis/docs/1.3.0/configuring-transports.html Cheers Martyn On Wed, Jun 22, 2016 at 7:18 AM, Sebastian Dellwig < sebastian.dellwig.ext@iqser.com> wrote: > yes, that's it. > It works now. I did not knew, that there is a correlation between acceptor > and connector. > > Thank you very much > -Sebastian > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Artemis-Automatic-failback-does-not-work-tp4713190p4713231.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > --94eb2c0717a223655c0535da808b--