Vilius Šumskas created ARTEMIS-3640:
---------------------------------------
Summary: external clients cannot use cluster topoligy for HA or
load balancing
Key: ARTEMIS-3640
URL: https://issues.apache.org/jira/browse/ARTEMIS-3640
Project: ActiveMQ Artemis
Issue Type: Bug
Reporter: Vilius Šumskas
Let's say there is a simple Artemis HA master/slave shared storage cluster with
such configuration:
{noformat}
<connectors>
<connector
name="artemis-master">tcp://internal-cluster-dns-1:61616</connector>
<connector
name="artemis-slave">tcp://internal-cluster-dns-2:61616</connector></connectors>
{noformat}
The cluster is using static discovery.
Factory on internal clients are using:
{code:java}
(tcp://internal-cluster-dns-1:61616,tcp://internal-cluster-dns-2:61616)?ha=true&reconnectAttempts=30&useTopologyForLoadBalancing=false{code}
Those internal clients can successfully connect to the cluster and failover
works as expected.
However if there is also external clients which use external DNS/IP address of
the cluster the topology doesn't return correct DNS name and the failover fails.
{noformat}
(tcp://external-cluster-dns-1:61616,tcp://external-cluster-dns-2:61616)?ha=true&reconnectAttempts=30&useTopologyForLoadBalancing=false{noformat}
{noformat}
org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector: AMQ214033:
Cannot resolve host java.net.UnknownHostException:
internal-cluster-dns-1{noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
