OK - I have it working. There was indeed a problem with the ActiveMQ servers
master / slave configs in the broker.xml files for each. The sections
, were entirely missing, and the
only had the local host defined, and not the other one.
Thank you Justin for pointing me in the right direction!
Thanks. It's running in a Docker container, so I "docker stop" it. I can
see the log output as the slave takes over and starts up, and then I can log
into the old slave's ActiveMQ management console. And, I can see that the
client detects the down master and attempts reconnects.
Having said tha
One more thing...
Since you're using share-store then you either need to really kill the
broker (e.g. kill -9 ) to trigger failover or set
true if you're stopping the
broker gracefully, e.g.:
true
Justin
On Mon, Jul 8, 2019 at 3:03 PM bob.sandif
Sorry about the code not showing up. I edited the post to put it in.
Thanks for the reply - a simple usage of your suggestion didn't work - but
it did change the behaviour, so I'll pursue the possible values for the
query params on the url specification.
Bob.
--
Sent from: http://activemq.228
None of the code or configuration came through on your first email. In the
second email it didn't come through either, but some of it is visible on
the Nabble web page.
That said, I think the problem is the URL you're using (i.e.
"(tcp://activemq-1:61616,tcp://activemq-2:61616)"). You aren't speci
Sorry - a couple of other things.
The exception I get on the client (when I shut down the master ActiveMQ) and
try to send a message to ActiveMQ is:
I'm using a URL like this:
I tried:
but got an exception like this:
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f234
I have a (I think) simple master / slave setup of ActiveMQ servers, using
shared file system. When I shut down the current master, it fails over to
the slave, and when I then restart the original master, it becomes the
standby - which is all just fine.
I'm having problems on the client side, thou
