t; --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/How-to-Force-a-Connection-Failover-in-an-
> ActiveMQ-Replicated-LevelDB-Cluster-tp4720385p4720571.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
The JMX operations "stop", "start" (or "restart") on the Master Broker do the
job.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/How-to-Force-a-Connection-Failover-in-an-ActiveMQ-Replicated-LevelDB-Cluster-tp4720385p4720571.html
Sent fr
I haven't personally tried this, but I'd expect that calling stop() on the
networkConnector for the master broker via JMX would do what you want
without requiring a full restart. (Then you could call start() to bring it
back, as the slave.) http://activemq.apache.org/jmx.html has a table that
lis
Currently I stop the ActiveMQ Master Node (by a systemd service) to force a
Slave become the new Master.
Afterwards I restart the stopped ActiveMQ Master Node (by a systemd
service) which will become a new Slave.
Is there another way to Force a Connection Failover without stopping and
restarting t
