[infinispan-issues] [JBoss JIRA] (ISPN-3876) TcpTransportFactory stores failed SocketAddress in RequestBalancingStrategy

[Mircea Markus (JIRA)]

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

Mircea Markus commented on ISPN-3876:
-------------------------------------

Thanks for reporting this!
This load balancing should be self-healing, assuming that you have at least one server running:
- when you cannot connect to a node, the next one is tried
- when an active node replies, it will return a list of the active servers and the load balancer should be updated

>From your comments, I understand this is not self healing, or? If so, do you have some nodes to reproduce this behavior? What version of ISPN are you using and how is the cache configured?

                
> TcpTransportFactory stores failed SocketAddress in RequestBalancingStrategy
> ---------------------------------------------------------------------------
>
>                 Key: ISPN-3876
>                 URL: https://issues.jboss.org/browse/ISPN-3876
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 5.2.1.Final, 5.3.0.Final, 6.0.0.Final
>         Environment: Hotrod Client, Java
>            Reporter: Patrick Seeber
>            Assignee: Mircea Markus
>
> The "updateServers" Method in the TcpTransportFactory class iterates over all addedServers and adds them to the connection pool if no exceptions are thrown. Howerver, if an exception is thrown, the SocketAddress may not have been added to the conection pool but is added to the balancer afterwards. Therefore, the balancer may contain an invalid SocketAddress which is not contained in the connection pool.
> In our application with few distributed caches, we encounter situations where all servers (SocketAddresses) are corrupt and the application fails to load or store entries in/from the cache.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira