activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <>
Subject Re: How to Force a Connection Failover in an ActiveMQ Replicated LevelDB Cluster ?
Date Sat, 17 Dec 2016 19:23:27 GMT
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.) has a table that
lists many of the JMX objects and their attributes and methods, for


On Dec 15, 2016 2:15 AM, "Patrick Vansevenant" <>

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 the Master broker ?
Perhaps by commands ? Perhaps by JMX or so ?


**** DISCLAIMER ****

"This message is delivered to all addressees subject to the conditions
set forth in the attached disclaimer, which is an integral part of this

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message