[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-47) Master node enters tight loop calling getClusterCoordinatorState on remote node

[Michal Babacek (JIRA)]

     [ https://issues.jboss.org/browse/MODCLUSTER-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Babacek closed MODCLUSTER-47.
------------------------------------



Closing. Clean-up.
At least one of the following applies:

  * the issue has been thoroughly tested as a part of one of the current releases
or
  * it hasn't occurred in ~2 years
or
  * it's utterly harmless

> Master node enters tight loop calling getClusterCoordinatorState on remote node
> -------------------------------------------------------------------------------
>
>                 Key: MODCLUSTER-47
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-47
>             Project: mod_cluster
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.0.0.Beta3
>            Reporter: Brian Stansberry
>            Assignee: Paul Ferraro
>            Priority: Critical
>             Fix For: 1.0.0.Beta4
>
>         Attachments: node1-modha.log, node2-modha.log
>
>
> 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 at 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 at 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



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)