Thank you Justin.
I can indeed see in your source code that this flag is being used all over
the place.
I am now using it and also using reconnectAttempts=-1 and things behave ok.
I ran into the issue in one of the client environments where clients did not
want to failover, as if locked in to the
The "ha" parameter tells the client to use the backup information it
receives from the broker so in case the original connection fails it will
automatically connect (i.e. failover) to the backup. Without ha=true on
your client URL you won't get true failover.
I believe what you're seeing is just t
So what exactly is the ha parameter for?
Does it treat servers somehow differently? E.g. *non-ha* pool of servers,
vs. *ha* pool of servers?
Form what I am seeing, even without it, client fails over to slave after
retrying master 5 times and then fail over to the slave... So the fail over
is someh
I'd say you're missing the ha flag. To enable failover you need to use
"ha=true" in your URL. Otherwise the client won't know that it's connection
to an HA (i.e. highly available) master/slave pair.
Justin
On Thu, Aug 1, 2019 at 6:35 AM mk666aim wrote:
> The below URL does not seem to work for
Also, in a scenario where master server is started again, and backup server
should fail back to the master from that moment onwards
Should the client also reconnect to the master? It does not seem to be
happening, as my client is still locked to the backup server.
When I shut down backup server
The below URL does not seem to work for me.
Client basically never switches to the backup node. Isn't that what
reconnectAttempts=-1 will cause?
I used following URL before and the switching happened:
*(tcp://master:61616,tcp://slave:61616)?reconnectAttempts=5*
What am I missing?
And what is th
Hi Justin,
thanks a lot for clarification. I couldn't find a documentation with all
supported URI schemes and all supported options for the Artemis JMS core
client. Maybe you have a link...
Frank
Thanks for following up, Frank. I would expect a URL like this to work:
(tcp://master:61616,tcp://slave:61616)?ha=true&reconnectAttempts=-1
Both "randomize" and "backup" are not used by the Artemis JMS core client.
Also, the "failover://" schema is used by OpenWire clients, not Artemis JMS
cor
Hello all,
there was an error in my broker.xml files on both master and slave. After
correcting these, the following URI is working with the "ActiveMQ JMS Core
Client" library (and also with the artemis command line clients), like it
should.
(tcp://master:61616,tcp://slave:61616)?ha=true&rec
Hello,
I've followed the test setup and installed a replicated static master/slave
environment (like documented here:
https://github.com/jbossdemocentral/amq-ha-replicated-demo). Version is Artemis
2.7.0. Both master and slave processes start without errors.
Now I try to find out which is th
10 matches
Mail list logo
