[
https://issues.jboss.org/browse/WFLY-4865?page=com.atlassian.jira.plugin....
]
Ian Kent commented on WFLY-4865:
--------------------------------
I did see the ISPN000260: error on the other one server… which is similar to what they
mention in
https://developer.jboss.org/thread/256781
2015-07-02 14:31:01,622 ERROR org.infinispan.remoting.InboundInvocationHandlerImpl
(remote-thread-45) ISPN000260: Exception executing command:
org.infinispan.statetransfer.OutdatedTopologyException: Cache topology changed while the
command was executing: expected 42, got 43
2015-07-02 14:31:16,640 ERROR org.infinispan.remoting.InboundInvocationHandlerImpl
(remote-thread-45) ISPN000260: Exception executing command:
org.infinispan.statetransfer.OutdatedTopologyException: Cache topology changed while the
command was executing: expected 42, got 43
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
Affects Versions: 8.2.0.Final
Reporter: Ian Kent
Assignee: Jason Greene
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).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)