Now that 2.1 is released you should be using that. You need to provide a network address:port or URL via the <network-check-list>. I don't believe it is sufficient to provide the address:port of the backup on the live and vice versa. The cluster nodes already have those addresses and ports by virtue of their clustering together. The whole point of the <network-check-list> is to provide a reference that is *outside* of the existing cluster to act as a kind of sentinel so the nodes can hopefully get a clearer understanding of whether or not they are isolated.
Justin ----- Original Message ----- From: "martk" <123mar...@web.de> To: users@activemq.apache.org Sent: Monday, May 15, 2017 11:49:45 PM Subject: Re: Artemis HA cluster with replication With master you are talking about the 2.2.0-SNAPSHOT? How do I have to provide the address? Is the (current) entry in the broker.xml (IP:PORT) enough? Shared storage is unfortunately no option (that is why trying to use Artemis). On Mon, May 15, 2017, Clebert Suconic wrote: > that's how it should work... > > Try master (current version now).. it should work.. > > You have to provide an address that's unique for both servers, and you can > use to validate if the local network is out. that is you need to solve > your network issues as well.. if you split the network there's no way araound. -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-HA-cluster-with-replication-tp4725734p4726186.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
