]
Rahul Jain commented on WFLY-4865:
----------------------------------
[~pferraro] Can you please let us know whether is there any workaround for this issue in
wildlfy version 8.2 or do we need to upgrade to 9.0 up to get the fix for this issue?
org.infinispan.util.concurrent.TimeoutException: Timed out waiting
for topology
-------------------------------------------------------------------------------
Key: WFLY-4865
URL:
https://issues.jboss.org/browse/WFLY-4865
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 8.2.0.Final
Reporter: Ian Kent
Assignee: Paul Ferraro
Fix For: 9.0.0.Final
We have a 10 ode wildfly cluster. We recently started getting the following exceptions in
one of our deployment environments. I checked wildfly docs, google, wildfly jira and
wildfly forums and cannot find a resolution. We are using default configuration for
jgroups and we are using a replicate async web cache.
{noformat}
2015-07-02 14:31:16,628 ERROR org.infinispan.interceptors.InvocationContextInterceptor
(clojure-agent-send-off-pool-10600) ISPN000136: Execution error:
org.infinispan.util.concurrent.TimeoutException: Timed out waiting for topology 43
2015-07-02 14:31:24,613 ERROR io.undertow.request (default task-27) UT005023: Exception
handling request to
/fault/elements/Node%3ABGVLPAAMT1A-P-AL-0294-01/monitoring-state/history:
java.lang.IllegalStateException: Address 10.70.19.243:10.70.19.243-0/web is no longer in
the cluster
{noformat}
The fact that this only happens on one of our clusters leads me to believe that it is
environmental (maybe network latency).