[ https://issues.apache.org/jira/browse/ARTEMIS-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17840888#comment-17840888 ]
ASF subversion and git services commented on ARTEMIS-4744: ---------------------------------------------------------- Commit ee7a2c0944843bf8b3ebb939f5833aa26b1e1868 in activemq-artemis's branch refs/heads/main from Timothy Bish [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=ee7a2c0944 ] ARTEMIS-4744 Fully support multple host broker connections URIs Create a new NettyConnector for each connection attempt that is configured from distinct broker connection URIs which allows for differing TLS configuration per remote connection configuration. > AMQP broker connections don't fully support multi host URIs > ----------------------------------------------------------- > > Key: ARTEMIS-4744 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4744 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP > Affects Versions: 2.33.0 > Reporter: Timothy A. Bish > Assignee: Timothy A. Bish > Priority: Major > Fix For: 2.34.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > When configuring a multi host connection URI for an AMQP broker connection > the connection will utilize some but not all of the configuration. The > broker will attempt connection to each host and port part specific on the URI > but does not apply configuration specific to a given host. This can lead to > failure on connect due to using the TLS configuration from the first host > when attempting to connect to the following N hosts. Users need to be able > to configure TLS specific options per host as values such as host > verification, SNI and trust stores can vary amongst hosts. -- This message was sent by Atlassian Jira (v8.20.10#820010)