Clebert,
I've modified broker.xml for master and slave as follows:
<cluster-connections>
<cluster-connection name="my-cluster">
<address>jms</address>
<connector-ref>artemis</connector-ref>
<connection-ttl>120000</connection-ttl>
<reconnect-attempts>-1</reconnect-attempts>
<message-load-balancing>ON_DEMAND</message-load-balancing>
<max-hops>0</max-hops>
<discovery-group-ref discovery-group-name="dg-group1"/>
</cluster-connection>
</cluster-connections>
and split brain still happening:
Master 23:22:56,401: AMQ222092: Connection to the backup node failed,
removing replication now
Slave 23:24:29,380: AMQ212037: Connection failure has been detected:
AMQ119011: Did not receive data from server for
org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnection@2eb88966[local=
/11.203.148.100:47219, remote=arthost1/11.203.148.100:41410]
[code=CONNECTION_TIMEDOUT]
23:25:17,667: AMQ221007: Server is now live
Master 23:25:19,645: AMQ212034: There are more than one servers on the
network broadcasting the same node id.
Slave 23:25:19,660: AMQ212034: There are more than one servers on the
network broadcasting the same node id.
Please note that master and slave are on the same box. Another point,
documentation states that reconnect-attempts is "The number of times the
system will try to reconnect to a node in the cluster."
Is a backup broker considered as "node"? Does reconnect-attempts apply to
master-slave reconnection attempts?
Will appreciate any help,
Boris
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
