[ARTEMIS-3640] external clients cannot use cluster topology for HA or load balancing

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.29.0
• Assignee: Domenico Francesco Bruscino
• Reporter: Vilius Šumskas
• Created: 12/Jan/22 12:44
• Updated: 21/Jun/23 13:54
• Resolved: 21/Jun/23 13:54

Description

Let's say there is a simple Artemis HA master/slave shared storage cluster with such configuration:

 

<connectors>
   <connector name="artemis-master">tcp://internal-cluster-dns-1:61616</connector>
   <connector name="artemis-slave">tcp://internal-cluster-dns-2:61616</connector>
</connectors>

The cluster is using static discovery.

 

Factory on internal clients are using:

(tcp://internal-cluster-dns-1:61616,tcp://internal-cluster-dns-2:61616)?ha=true&reconnectAttempts=30&useTopologyForLoadBalancing=false

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.

(tcp://external-cluster-dns-1:61616,tcp://external-cluster-dns-2:61616)?ha=true&reconnectAttempts=30&useTopologyForLoadBalancing=false

org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector: AMQ214033: Cannot resolve host java.net.UnknownHostException: internal-cluster-dns-1

 

Issue Links

• links to: GitHub Pull Request #4394