Thank you! We will try to apply your suggestions.
One last thing, as I understood the proper URL string for external clients then
would be:
(tcp://external-cluster-dns-1:61616,tcp://external-cluster-dns-2:61616)?ha=false&useTopologyForLoadBalancing=false&initialConnectAttempts=2&failoverOnInitial
that makes sense, any failover reconnect will use the topology
information, that will be wrong.
you need to have artemis not do any reconnect,
initialConnectAttempts=2 and on initial connection, it will choose the
first working url from the two external dns names configured.
You can get the failove
Thanks, Gary. Ticket created https://issues.apache.org/jira/browse/ARTEMIS-3640
We experimented a little bit more with this and found that if we use any of the
following parameters failover fails:
retryIntervalMultiplier=2,reconnectAttempts=1000,maxRetryInterval=12
However if we remove these
there is a problem here, currently there is no way to "transform" the
host information in the topology update commands. the topology is used
for ha and for loadbalancing and the client will always end up with
the internal dns name via the topology update.
This needs an enhancement, some thing alon
