Uploaded image for project: 'mod_cluster'
  1. mod_cluster
  2. MODCLUSTER-47

Master node enters tight loop calling getClusterCoordinatorState on remote node

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 1.0.0.Beta4
    • 1.0.0.Beta3
    • None
    • None

    Description

      To reproduce:

      1) Install the mod_cluster 1.0.0.Beta3 sar on two nodes.
      2) Configure a value for the proxyList config (don't know if this is relevant, just the way my setup is)
      3) Add a war that's not excluded to both nodes
      4) Start node1
      5) Start node2

      After node2 starts, node1's background thread goes into a loop calling getCoordinatorState on the other node, repeating as soon as a response is received:

      2009-02-03 16:36:08,120 DEBUG [org.jboss.modcluster.ha.HAModClusterService] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Check status for engine [jboss.web]
      2009-02-03 16:36:08,122 TRACE [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) callMethodOnCluster(true), objName=HAModClusterService, methodName=getClusterCoordinatorState, members=[192.168.1.146:58895]
      2009-02-03 16:36:08,125 TRACE [org.jboss.ha.framework.server.ClusterPartition$RpcHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) dests=[192.168.1.146:58895], method_call=HAModClusterService.getClusterCoordinatorState([MCMPServerStateImpl

      {address=/127.0.0.1,port=6666,state=OK,establishedtrue}]), mode=2, timeout=60000
      2009-02-03 16:36:08,126 TRACE [org.jboss.ha.framework.server.ClusterPartition$RpcHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) real_dests=[192.168.1.146:58895]
      2009-02-03 16:36:08,184 TRACE [org.jboss.ha.framework.server.ClusterPartition$RpcHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) responses: [sender=192.168.1.146:58895, retval=org.jboss.modcluster.ha.rpc.ModClusterServiceStateGroupRpcResponse@37bb7c19, received=true, suspected=false]
      2009-02-03 16:36:08,187 TRACE [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) callMethodOnCluster(true), objName=HAModClusterService, methodName=getClusterCoordinatorState, members=[192.168.1.146:58895]
      2009-02-03 16:36:08,187 TRACE [org.jboss.ha.framework.server.ClusterPartition$RpcHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) dests=[192.168.1.146:58895], method_call=HAModClusterService.getClusterCoordinatorState([MCMPServerStateImpl{address=/127.0.0.1,port=6666,state=OK,establishedtrue}

      ]), mode=2, timeout=60000
      2009-02-03 16:36:08,187 TRACE [org.jboss.ha.framework.server.ClusterPartition$RpcHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) real_dests=[192.168.1.146:58895]
      2009-02-03 16:36:08,199 TRACE [org.jboss.ha.framework.server.ClusterPartition$RpcHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) responses: [sender=192.168.1.146:58895, retval=org.jboss.modcluster.ha.rpc.ModClusterServiceStateGroupRpcResponse@1d64d42f, received=true, suspected=false]
      2009-02-03 16:36:08,199 TRACE [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) callMethodOnCluster(true), objName=HAModClusterService, methodName=getClusterCoordinatorState, members=[192.168.1.146:58895]

      and so on

      Attachments

        Activity

          People

            pferraro@redhat.com Paul Ferraro
            bstansbe@redhat.com Brian Stansberry
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: