[infinispan-issues] [JBoss JIRA] (ISPN-2139) ping_on_startup ignored
Michal Linhard (JIRA)
jira-events at lists.jboss.org
Mon Jul 9 17:06:12 EDT 2012
[ https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705041#comment-12705041 ]
Michal Linhard commented on ISPN-2139:
--------------------------------------
To me the purpose of the second ping
https://github.com/infinispan/infinispan/blob/master/client/hotrod-client/src/main/java/org/infinispan/client/hotrod/RemoteCacheManager.java#L521
seems like it's solely to return PingResult, which you can't get from getTransport()
That way you can check whether the cache you're getting via getCache(namedCache) exists on the remote side.
> 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: Dan Berindei
> 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
More information about the infinispan-issues
mailing list