Alex,
I think we're talking about different things here. I understand _in
general_ how ports for different protocols, etc. would be useful. The
default broker.xml defines multiple ports for this very reason. My question
is specifically about this user's situation with the cluster-connection and
th
Hi Justin,
There may be a reason to have different listeners, protocols and
other settings for servers and for clients.
For example, Apache Kafka can use different listeners for connections
between servers and advertised listeners for the clients:
https://kafka.apache.org/documentation/#brokerconf
You are seeing the expected behavior.
This is because the URL you provide to the Core client is only used for the
initial connection by default. Once the initial connection is made the
broker informs the client about the cluster topology (if one exists), and
when reconnecting or failing over the c
Hello Community,
I'm testing a clustered setup with two ActiveMQ Artemis brokers configured
for high availability. Each broker has two acceptors: one for client
connections on port and one for cluster connections on port 6000.
In my test application, I connect using a failover URL:
(tcp://
