2:33 a.m.
Michal Linhard created ISPN-2139:
------------------------------------
Summary: 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: Manik Surtani
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
5:55 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
Michal Linhard commented on ISPN-2139:
--------------------------------------
Now that I'm reading the code, the start() method isn't even supposed to ping,
I guess the problem is then, that the ping() operation is called from
RCM.createRemoteCache() without checking the ping_on_startup param.
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: Manik Surtani
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
7:14 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
Manik Surtani reassigned ISPN-2139:
-----------------------------------
Assignee: Mircea Markus (was: Manik Surtani)
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
7:14 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
Manik Surtani updated ISPN-2139:
--------------------------------
Fix Version/s: 5.1.x
5.2.0.ALPHA2
5.2.0.FINAL
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
9:43 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
Galder Zamarreño reassigned ISPN-2139:
--------------------------------------
Assignee: Dan Berindei (was: Mircea Markus)
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
9:43 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
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
2:50 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-2139:
------------------------------------
Galder, I didn't actually add the ping call, I just added another ping() method in RCM
that wrapped the existing cache.ping() call in order to pass the Transport as a
parameter.
Actually, I think the ping() was first added in your commit for ISPN-990 :)
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
4:06 p.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
Michal Linhard commented on ISPN-2139:
--------------------------------------
To me the purpose of the second ping
https://github.com/infinispan/infinispan/blob/master/client/hotrod-client...
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
2:23 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
Galder Zamarreño reassigned ISPN-2139:
--------------------------------------
Assignee: Galder Zamarreño (was: Dan Berindei)
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.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
2:25 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
Work on ISPN-2139 started by Galder Zamarreño.
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.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
2:45 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2139:
----------------------------------------
@Dan, @Michal, thx for the clarifications.
There's two ways to fix this:
1. Make ping be a retry-on-failure operation, but that's not really the intention of
the operation. The idea of ping is to check whether a particular server is up or down. As
Michal said, we're reusing ping to check whether a cache name is defined in the remote
server too.
2. Make the cache name in getCache() be controllable by ping_on_startup. This sounds more
sensible.
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.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
3:38 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-2139:
-----------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/1209
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.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
6:13 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2139:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
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.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
8:31 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-2139:
-----------------------------------
Fix Version/s: (was: 5.1.x)
Git Pull Request: https://github.com/infinispan/infinispan/pull/1209 (was:
https://github.com/infinispan/infinispan/pull/1209)
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.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
8:51 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration updated ISPN-2139:
------------------------------------------
Git Pull Request: https://github.com/infinispan/infinispan/pull/1209 (was:
https://github.com/infinispan/infinispan/pull/1209)
Bugzilla Update: Perform
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.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
8:51 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration updated ISPN-2139:
------------------------------------------
Git Pull Request: https://github.com/infinispan/infinispan/pull/1209 (was:
https://github.com/infinispan/infinispan/pull/1209)
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=841892
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.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
4:56 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
Tristan Tarrant updated ISPN-2139:
----------------------------------
Fix Version/s: 5.1.6.FINAL (JDG)
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=841892 (was:
https://bugzilla.redhat.com/show_bug.cgi?id=841892)
Git Pull Request: https://github.com/infinispan/infinispan/pull/1209 (was:
https://github.com/infinispan/infinispan/pull/1209)
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
9:57 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on ISPN-2139:
-----------------------------------------------
Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug
841892|https://bugzilla.redhat.com/show_bug.cgi?id=841892] from NEW to MODIFIED
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
11:39 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on ISPN-2139:
-----------------------------------------------
Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug
841892|https://bugzilla.redhat.com/show_bug.cgi?id=841892] from MODIFIED to ON_QA
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
8:50 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
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
8:54 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on ISPN-2139:
-----------------------------------------------
Michal Linhard <mlinhard(a)redhat.com> changed the Status of [bug
841892|https://bugzilla.redhat.com/show_bug.cgi?id=841892] from ON_QA to ON_DEV
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
9:50 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on ISPN-2139:
-----------------------------------------------
Michal Linhard <mlinhard(a)redhat.com> changed the Status of [bug
841892|https://bugzilla.redhat.com/show_bug.cgi?id=841892] from ON_DEV to ASSIGNED
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
9:42 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
Tristan Tarrant updated ISPN-2139:
----------------------------------
Fix Version/s: 5.1.x
(was: 5.2.0.FINAL)
(was: 5.2.0.ALPHA2)
(was: 5.1.6.FINAL (JDG))
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.x
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
5:54 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
Galder Zamarreño resolved ISPN-2139.
------------------------------------
Fix Version/s: 5.1.6.FINAL
5.2.0.FINAL
5.2.0.ALPHA2
(was: 5.1.x)
Resolution: Done
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, 5.2.0.FINAL, 5.2.0.ALPHA2
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
6:01 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2139:
----------------------------------------
Since the associated fix versions were released, please avoid reopening the JIRA and
simply create a new one with the right affects versions.
What is it that you're seeing exactly? I added a test to verify that ping_on_startup
disabling worked...
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, 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
6:25 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on ISPN-2139:
-----------------------------------------------
Michal Linhard <mlinhard(a)redhat.com> made a comment on [bug
841892|https://bugzilla.redhat.com/show_bug.cgi?id=841892]
When getCache is called the ping is done regardless of ping_on_startup flag. The only
effect ping_on_startup has is preventing first ping in TransportObjectFactory.makeObject
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, 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
9:24 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-2139:
-----------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=841892 (was:
https://bugzilla.redhat.com/show_bug.cgi?id=841892)
Git Pull Request: https://github.com/infinispan/infinispan/pull/1209 (was:
https://github.com/infinispan/infinispan/pull/1209)
Forum Reference:
http://lists.jboss.org/pipermail/infinispan-dev/2012-August/011072.html
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, 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
6:54 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on ISPN-2139:
-----------------------------------------------
Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug
841892|https://bugzilla.redhat.com/show_bug.cgi?id=841892] from ASSIGNED to MODIFIED
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, 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
6:54 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration updated ISPN-2139:
------------------------------------------
Git Pull Request: https://github.com/infinispan/infinispan/pull/1209 (was:
https://github.com/infinispan/infinispan/pull/1209)
Bugzilla Update: (was: Perform)
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=841892 (was:
https://bugzilla.redhat.com/show_bug.cgi?id=841892)
Forum Reference:
http://lists.jboss.org/pipermail/infinispan-dev/2012-August/011072.html (was:
http://lists.jboss.org/pipermail/infinispan-dev/2012-August/011072.html)
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, 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
6:54 a.m.
[
https://issues.jboss.org/browse/ISPN-2139?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration updated ISPN-2139:
------------------------------------------
Git Pull Request: https://github.com/infinispan/infinispan/pull/1209 (was:
https://github.com/infinispan/infinispan/pull/1209)
Bugzilla References: (was: https://bugzilla.redhat.com/show_bug.cgi?id=841892)
Forum Reference:
http://lists.jboss.org/pipermail/infinispan-dev/2012-August/011072.html (was:
http://lists.jboss.org/pipermail/infinispan-dev/2012-August/011072.html)
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, 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
4507
days inactive
4562
days old
infinispan-issues@lists.jboss.org
29 comments
7 participants
participants (7)
-
Dan Berindei (JIRA) -
Galder Zamarreño (JIRA)
-
Manik Surtani (JIRA)
-
Michal Linhard (JIRA)
-
Mircea Markus (JIRA)
-
RH Bugzilla Integration (JIRA)
-
Tristan Tarrant (JIRA)