[
https://issues.apache.org/jira/browse/ARTEMIS-4744?focusedWorklogId=916401&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-916401
]
ASF GitHub Bot logged work on ARTEMIS-4744:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 25/Apr/24 14:45
Start Date: 25/Apr/24 14:45
Worklog Time Spent: 10m
Work Description: tabish121 opened a new pull request, #4906:
URL: https://github.com/apache/activemq-artemis/pull/4906
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.
Issue Time Tracking
-------------------
Worklog Id: (was: 916401)
Remaining Estimate: 0h
Time Spent: 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: 10m
> 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)
