[infinispan-issues] [JBoss JIRA] (ISPN-2139) ping_on_startup ignored

[Galder Zamarreño (JIRA)]

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

Galder Zamarreño commented on ISPN-2139:
----------------------------------------

Hmmm, TcpTransportFactory.start() is the one making use of ping on startup property. 

But seems like RCM.getCache() is doing it too, after calling transportFactory.getTransport() (which would have done the ping if configured to do so). This added ping() called seems to come from the code that Dan added in ISPN-1020.

@Dan, can you clarify why you added this apparently superfluous ping call? 
                
> ping_on_startup ignored
> -----------------------
>
>                 Key: ISPN-2139
>                 URL: https://issues.jboss.org/browse/ISPN-2139
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 5.1.5.FINAL
>            Reporter: Michal Linhard
>            Assignee: Mircea Markus
>              Labels: jdg6
>             Fix For: 5.1.x, 5.2.0.ALPHA2, 5.2.0.FINAL
>
>
> When a configuration property 
> infinispan.client.hotrod.ping_on_startup=false
> is passed to the properties of RemoteCacheManager, this
> avoids ping in RemoteCacheManager.start() but
> RemoteCacheManager.getCache() does ping without checking this property
> and thus rendering this setting useless for scenario
> where we want to specify
> infinispan.client.hotrod.server_list
> with list of servers with some of the servers possibly not available yet.
> In such case we would expect the client to failover to first working server
> and retrying the first operation we want to do with the cache.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira