ARTEMIS-6004 Add clientFailoverAdvertisingEnabled configuration to not send failover server list info to AMQP clients - #6614
Open
KalCramer wants to merge 1 commit into
Open
Conversation
…t send failover server list info to AMQP clients
KalCramer
force-pushed
the
amqp_failover_list_flag
branch
from
August 13, 2026 17:43
847191b to
0900aed
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Add a
clientFailoverAdvertisingEnabledconnector property to control whether a backup connector is advertised to clients as part of the AMQP failover topology.Currently, Artemis can advertise the backup connector from the broker's internal cluster topology to AMQP clients. This can cause clients using different internal and external DNS names or ports to receive an unreachable failover endpoint.
For example, an external Qpid JMS client may initially connect using:
but receive the internal backup connector from the broker topology:
The client can then attempt to use the advertised endpoint instead of the endpoint configured by the client.
This is the scenario described in ARTEMIS-6004.
Changes
clientFailoverAdvertisingEnabledconnector property.trueto preserve existing behavior.false, the backup connector is not included in the AMQP failover information advertised to clients.Testing
The change was tested with a Java Qpid JMS client using an Artemis HA live/backup configuration where the broker's internal cluster topology uses different hostnames/ports from those exposed to external clients.
With:
the broker no longer advertises the internal backup connector to the AMQP client.
As a result, external clients no longer need to configure:
to prevent Qpid JMS from replacing their configured failover endpoints with the broker-provided topology.
This provides a broker-side solution for clients that cannot be configured with
failover.amqpOpenServerListAction=IGNORE.