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

RPCs to non-existant FORK channel are dropped

    XMLWordPrintable

    Details

    • Steps to Reproduce:
      Hide

      When starting multiple nodes at once, errors such as the following are commonly seen:

      WARN [org.infinispan.topology.ClusterTopologyManagerImpl] (transport-thread--p14-t10) ISPN000197: Error updating cluster member list: org.infinispan.util.concurrent.TimeoutException: Replication timeout for node2

      Show
      When starting multiple nodes at once, errors such as the following are commonly seen: WARN [org.infinispan.topology.ClusterTopologyManagerImpl] (transport-thread--p14-t10) ISPN000197: Error updating cluster member list: org.infinispan.util.concurrent.TimeoutException: Replication timeout for node2
    • Affects:
      Release Notes
    • Workaround Description:
      Hide

      Staggered startup of the nodes appears to help mitigate the issues.

      Show
      Staggered startup of the nodes appears to help mitigate the issues.

      Description

      RPCs sent to a FORK channel that is not currently running are not responded to correctly, causing the caller to eventually time out.

      An error response is being sent by org.jboss.as.clustering.jgroups.JChannelFactory, but the request ID is hard-coded to 0 so the reply can not be routed back to the sender and gets dropped.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  dereed Dennis Reed
                  Reporter:
                  dereed Dennis Reed
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: