You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/05/05 20:37:00 UTC

[jira] [Commented] (QPIDJMS-536) Failover URIs should not be deduplicated based on name resolution

    [ https://issues.apache.org/jira/browse/QPIDJMS-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17339885#comment-17339885 ] 

ASF subversion and git services commented on QPIDJMS-536:
---------------------------------------------------------

Commit f0788dee4c8129a1f7414ed7fd6884b7631e536a in qpid-jms's branch refs/heads/main from Stephen Nimmo
[ https://gitbox.apache.org/repos/asf?p=qpid-jms.git;h=f0788de ]

QPIDJMS-536 Remove InetAddress.getByName lookup for compare

URIs should be able to resolve to the same IP address, as the brokers may be running behind a proxy and
the remote will select the appropraite ultimate destination based on service name lookups etc. Updated
tests to remove constraints around resolving the URI back to an IP Address.


> Failover URIs should not be deduplicated based on name resolution
> -----------------------------------------------------------------
>
>                 Key: QPIDJMS-536
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-536
>             Project: Qpid JMS
>          Issue Type: New Feature
>          Components: qpid-jms-client
>    Affects Versions: 0.58.0
>            Reporter: Timothy A. Bish
>            Assignee: Timothy A. Bish
>            Priority: Major
>             Fix For: 0.59.0
>
>
> Up to now the failover provider resolved the address of the hostname's given and deduplicated then to avoid unnecessary duplication of connection attempts in the case where a user configured multiple failover locations that resolved to the same location.  Historically this had some minor benefit but in the service driven environments the client connects to today this can cause issue as different hosts might resolve to the same proxy ingress and be rerouted from there.   To that end we should remove the deduplication based on resolution and simply check for exact hostname matches where the port value is also a match. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org