Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-4865

org.infinispan.util.concurrent.TimeoutException: Timed out waiting for topology

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Out of Date
    • Affects Version/s: 8.2.0.Final
    • Fix Version/s: 9.0.0.Final
    • Component/s: Clustering
    • Labels:
      None

      Description

      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.

      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
      

      The fact that this only happens on one of our clusters leads me to believe that it is environmental (maybe network latency).

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                pferraro Paul Ferraro
                Reporter:
                iankent Ian Kent
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: