[infinispan-issues] [JBoss JIRA] (ISPN-7955) Hot Rod client needs to re-resolve topology addresses after failure to connect

[Radim Vansa (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-7955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492927#comment-13492927 ] 

Radim Vansa commented on ISPN-7955:
-----------------------------------

[~NadirX] I am afraid that this could lead to duplicities in connection pool: the per-server limits cannot be enforced when the address is not resolved as unresolved and resolved {{SocketAddress}} are not equal. Therefore, if client has {{localhost:11222}} in initial server list and the topology update will give you 127.0.0.1:11222 these will be considered different servers.

> Hot Rod client needs to re-resolve topology addresses after failure to connect
> ------------------------------------------------------------------------------
>
>                 Key: ISPN-7955
>                 URL: https://issues.jboss.org/browse/ISPN-7955
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Remote Protocols
>    Affects Versions: 8.2.6.Final, 8.1.7.Final, 9.1.0.Beta1, 9.0.3.Final
>            Reporter: Tristan Tarrant
>            Assignee: Tristan Tarrant
>             Fix For: 8.1.9.Final, 9.1.0.Final, 9.0.4.Final, 8.2.8.Final
>
>
> The Hot Rod client resolves topology addresses on reception. In dynamic environments where server nodes can restart with different IPs (but maintaining their external hostname) this causes the client to fail to reconnect. The client should hold on to the original address and re-resolve it in case of failures.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)