[ https://issues.apache.org/jira/browse/ARTEMIS-4744?focusedWorklogId=916476&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-916476 ]
ASF GitHub Bot logged work on ARTEMIS-4744: ------------------------------------------- Author: ASF GitHub Bot Created on: 25/Apr/24 17:29 Start Date: 25/Apr/24 17:29 Worklog Time Spent: 10m Work Description: gemmellr merged PR #4906: URL: https://github.com/apache/activemq-artemis/pull/4906 Issue Time Tracking ------------------- Worklog Id: (was: 916476) Time Spent: 1h 20m (was: 1h 10m) > 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)