It's my understanding that only the master broker's web console will be active and the slaves' won't operate till the slave becomes the master, though I've never personally tested that. But it certainly seems consistent with the behavior you're seeing.
Tim On May 1, 2016 10:29 AM, "sekaijin" <jean-yves.terr...@sap.aphp.fr> wrote: I've found this config https://github.com/dlaube/amq-example/blob/master/apache-activemq-5.9.0/examples/conf/activemq-leveldb-replicating.xml I've duplicated it on my 3 brokers (and changed the TCP port) All activeMQ starts but only one web console are working (the number 3) the log of others brokers display a jetty error : broker is not running. But the status command display broker is running I've send a message in foo.bar queue with web console I've stopped the broker 3 And I can see now the broker 2 in web console The foo.bar queue in this broker exist but is empty I've lost my message. I'm trying to make a active/active cluster not master/slave. I need to secure it. I can't lost any messages. A+JYT PS I'm running activeMQ 5.11.1 and zookeeper 3.4.6 -- View this message in context: http://activemq.2283324.n4.nabble.com/broker-network-replicated-levelDB-config-problem-tp4711416p4711417.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
