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....@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. >
