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

[Michal Linhard (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Linhard reopened ISPN-2139:
----------------------------------



Hi,
I'm just looking at this in 5.1.6.FINAL and the flag infinispan.client.hotrod.ping_on_startup
is still ignored - the ping is done regardless of it.

I guess it's not a good thing not doing the ping
because of the cache name validation at least.

Shouldn't we remove the flag infinispan.client.hotrod.ping_on_startup completely ? As of now it's of no use.
Before releasing 5.2.0 is good time to do this.
                
> 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: Galder Zamarreño
>              Labels: jdg6
>             Fix For: 5.1.6.FINAL (JDG), 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