Tomcat Cluster - node02 is invalid, removed or not replicated at this node.
Hello guys! We are trying to test Tomcat clustering but we are getting some problems. Sometimes (Log2) everything works fine but in other cases the cluster doesn't work (Log1). The only difference is the time that we wait after we shutdown a node. When we make a request after shutdown a node, cluster doesn't work, but if we wait more time (1 minute more or less), the cluster works fine and we can proceed making requests. Log 1: 22/Fev/2008 10:31:11 org.apache.catalina.cluster.tcp.ReplicationValvecreatePrimaryIndicator FINE: Context /outpatient: Primarity of session 1E4B56ED32E80A15EE5B40E5C83FB49E.node02 in request attribute org.apache.catalina.cluster.tcp.isPrimarySession is false. 22/Fev/2008 10:31:11 org.apache.catalina.cluster.tcp.SimpleTcpClusterlogSendMessage INFO: SEND 22/Fev/2008:10:31:11 16 - 1E4B56ED32E80A15EE5B40E5C83FB49E.node02#-#localhost#-#/outpatient#-#0#-#1203676271418 22/Fev/2008 10:31:13 org.apache.catalina.cluster.tcp.ReplicationValveresetDeltaRequest FINE: Cluster is standalone: reset Session Request Delta at context /outpatient 22/Fev/2008 10:31:15 org.apache.catalina.cluster.tcp.ReplicationValvecreatePrimaryIndicator FINE: Context /outpatient: Requested session 1E4B56ED32E80A15EE5B40E5C83FB49E.node02 is invalid, removed or not replicated at this node. Log 2: 22/Fev/2008 10:34:08 org.apache.catalina.cluster.tcp.ReplicationValvecreatePrimaryIndicator FINE: Context /outpatient: Primarity of session 76CFC5DD3CF130EA0A10875E7B7C.node01 in request attribute org.apache.catalina.cluster.tcp.isPrimarySession is false. 22/Fev/2008 10:34:08 org.apache.catalina.cluster.tcp.SimpleTcpClusterlogSendMessage INFO: SEND 22/Fev/2008:10:34:08 2 - 76CFC5DD3CF130EA0A10875E7B7C.node01#-#localhost#-#/outpatient#-#0#-#1203676448864 22/Fev/2008 10:34:10 org.apache.catalina.cluster.tcp.ReplicationValveresetDeltaRequest FINE: Cluster is standalone: reset Session Request Delta at context /outpatient 22/Fev/2008 10:34:38 org.apache.catalina.cluster.tcp.ReplicationValvecreatePrimaryIndicator FINE: Context /outpatient: Primarity of session 76CFC5DD3CF130EA0A10875E7B7C.node02 in request attribute org.apache.catalina.cluster.tcp.isPrimarySession is true. Our cluster setup: Cluster className=org.apache.catalina.cluster.tcp.SimpleTcpCluster doClusterLog=true clusterLogName=clusterlog manager.className= org.apache.catalina.cluster.session.DeltaManager manager.expireSessionsOnShutdown=false manager.notifyListenersOnReplication=false manager.notifySessionListenersOnReplication=false manager.sendAllSessions=false manager.sendAllSessionsSize=500 manager.sendAllSessionsWaitTime=20 Membership className= org.apache.catalina.cluster.mcast.McastService mcastAddr=228.0.0.4 mcastClusterDomain=d10 mcastPort=45564 mcastFrequency=1000 mcastDropTime=1000 recoveryCounter=10 recoveryEnabled=true recoverySleepTime=5000/ Receiver className= org.apache.catalina.cluster.tcp.ReplicationListener tcpListenAddress=auto tcpListenPort=9016 tcpSelectorTimeout=100 tcpThreadCount=6/ Sender className= org.apache.catalina.cluster.tcp.ReplicationTransmitter replicationMode=fastasyncqueue recoverTimeout=500 stateTransferTimeout=1 recoverCounter=6 doTransmitterProcessingStats=true doProcessingStats=true doWaitAckStats=true queueTimeWait=true queueDoStats=true queueCheckLock=true ackTimeout=1500 waitForAck=true keepAliveTimeout=8 keepAliveMaxRequestCount=-1/ Valve className= org.apache.catalina.cluster.tcp.ReplicationValve filter=.*\.gif;.*\.js;.*\.css;.*\.png;.*\.jpeg;.*\.jpg;.*\.htm;.*\.html;.*\.txt; primaryIndicator=true debug=1 /
Re: Tomcat Cluster - node02 is invalid, removed or not replicated at this node.
HI Andrew, Your mcastDropTime=1000 is to low. Please set it to 3 and it is true that you must wait 35 sec before you can restart a cluster node. Use the Java Service Wrapper or add this to your start scripts to configure this. Peter Am 22.02.2008 um 11:48 schrieb Andrew Hole: Hello guys! We are trying to test Tomcat clustering but we are getting some problems. Sometimes (Log2) everything works fine but in other cases the cluster doesn't work (Log1). The only difference is the time that we wait after we shutdown a node. When we make a request after shutdown a node, cluster doesn't work, but if we wait more time (1 minute more or less), the cluster works fine and we can proceed making requests. Log 1: 22/Fev/2008 10:31:11 org.apache.catalina.cluster.tcp.ReplicationValvecreatePrimaryIndicator FINE: Context /outpatient: Primarity of session 1E4B56ED32E80A15EE5B40E5C83FB49E.node02 in request attribute org.apache.catalina.cluster.tcp.isPrimarySession is false. 22/Fev/2008 10:31:11 org.apache.catalina.cluster.tcp.SimpleTcpClusterlogSendMessage INFO: SEND 22/Fev/2008:10:31:11 16 - 1E4B56ED32E80A15EE5B40E5C83FB49E.node02#-#localhost#-#/outpatient#- #0#-#1203676271418 22/Fev/2008 10:31:13 org.apache.catalina.cluster.tcp.ReplicationValveresetDeltaRequest FINE: Cluster is standalone: reset Session Request Delta at context /outpatient 22/Fev/2008 10:31:15 org.apache.catalina.cluster.tcp.ReplicationValvecreatePrimaryIndicator FINE: Context /outpatient: Requested session 1E4B56ED32E80A15EE5B40E5C83FB49E.node02 is invalid, removed or not replicated at this node. Log 2: 22/Fev/2008 10:34:08 org.apache.catalina.cluster.tcp.ReplicationValvecreatePrimaryIndicator FINE: Context /outpatient: Primarity of session 76CFC5DD3CF130EA0A10875E7B7C.node01 in request attribute org.apache.catalina.cluster.tcp.isPrimarySession is false. 22/Fev/2008 10:34:08 org.apache.catalina.cluster.tcp.SimpleTcpClusterlogSendMessage INFO: SEND 22/Fev/2008:10:34:08 2 - 76CFC5DD3CF130EA0A10875E7B7C.node01#-#localhost#-#/outpatient#- #0#-#1203676448864 22/Fev/2008 10:34:10 org.apache.catalina.cluster.tcp.ReplicationValveresetDeltaRequest FINE: Cluster is standalone: reset Session Request Delta at context /outpatient 22/Fev/2008 10:34:38 org.apache.catalina.cluster.tcp.ReplicationValvecreatePrimaryIndicator FINE: Context /outpatient: Primarity of session 76CFC5DD3CF130EA0A10875E7B7C.node02 in request attribute org.apache.catalina.cluster.tcp.isPrimarySession is true. Our cluster setup: Cluster className=org.apache.catalina.cluster.tcp.SimpleTcpCluster doClusterLog=true clusterLogName=clusterlog manager.className= org.apache.catalina.cluster.session.DeltaManager manager.expireSessionsOnShutdown=false manager.notifyListenersOnReplication=false manager.notifySessionListenersOnReplication=false manager.sendAllSessions=false manager.sendAllSessionsSize=500 manager.sendAllSessionsWaitTime=20 Membership className= org.apache.catalina.cluster.mcast.McastService mcastAddr=228.0.0.4 mcastClusterDomain=d10 mcastPort=45564 mcastFrequency=1000 mcastDropTime=1000 recoveryCounter=10 recoveryEnabled=true recoverySleepTime=5000/ Receiver className= org.apache.catalina.cluster.tcp.ReplicationListener tcpListenAddress=auto tcpListenPort=9016 tcpSelectorTimeout=100 tcpThreadCount=6/ Sender className= org.apache.catalina.cluster.tcp.ReplicationTransmitter replicationMode=fastasyncqueue recoverTimeout=500 stateTransferTimeout=1 recoverCounter=6 doTransmitterProcessingStats=true doProcessingStats=true doWaitAckStats=true queueTimeWait=true queueDoStats=true queueCheckLock=true ackTimeout=1500 waitForAck=true keepAliveTimeout=8
Re: Tomcat Cluster - node02 is invalid, removed or not replicated at this node.
Thanks. Some more questions: -- In a scenario with two nodes, if I shutdown one, the other is instantly ready to receive and respond to requests, or it is necessary to wait a while? In a procuction scenario we cannot wait, because requests are frequently. -- The 35 seconds refers to the initial time? -- Is there any recommended configuration (basically If one tomcat crashes I want that the other responds immediatly to the requests)? Thanks a lot On Fri, Feb 22, 2008 at 1:38 PM, Peter Rossbach [EMAIL PROTECTED] wrote: HI Andrew, Your mcastDropTime=1000 is to low. Please set it to 3 and it is true that you must wait 35 sec before you can restart a cluster node. Use the Java Service Wrapper or add this to your start scripts to configure this. Peter Am 22.02.2008 um 11:48 schrieb Andrew Hole: Hello guys! We are trying to test Tomcat clustering but we are getting some problems. Sometimes (Log2) everything works fine but in other cases the cluster doesn't work (Log1). The only difference is the time that we wait after we shutdown a node. When we make a request after shutdown a node, cluster doesn't work, but if we wait more time (1 minute more or less), the cluster works fine and we can proceed making requests. Log 1: 22/Fev/2008 10:31:11 org.apache.catalina.cluster.tcp.ReplicationValvecreatePrimaryIndicator FINE: Context /outpatient: Primarity of session 1E4B56ED32E80A15EE5B40E5C83FB49E.node02 in request attribute org.apache.catalina.cluster.tcp.isPrimarySession is false. 22/Fev/2008 10:31:11 org.apache.catalina.cluster.tcp.SimpleTcpClusterlogSendMessage INFO: SEND 22/Fev/2008:10:31:11 16 - 1E4B56ED32E80A15EE5B40E5C83FB49E.node02#-#localhost#-#/outpatient#- #0#-#1203676271418 22/Fev/2008 10:31:13 org.apache.catalina.cluster.tcp.ReplicationValveresetDeltaRequest FINE: Cluster is standalone: reset Session Request Delta at context /outpatient 22/Fev/2008 10:31:15 org.apache.catalina.cluster.tcp.ReplicationValvecreatePrimaryIndicator FINE: Context /outpatient: Requested session 1E4B56ED32E80A15EE5B40E5C83FB49E.node02 is invalid, removed or not replicated at this node. Log 2: 22/Fev/2008 10:34:08 org.apache.catalina.cluster.tcp.ReplicationValvecreatePrimaryIndicator FINE: Context /outpatient: Primarity of session 76CFC5DD3CF130EA0A10875E7B7C.node01 in request attribute org.apache.catalina.cluster.tcp.isPrimarySession is false. 22/Fev/2008 10:34:08 org.apache.catalina.cluster.tcp.SimpleTcpClusterlogSendMessage INFO: SEND 22/Fev/2008:10:34:08 2 - 76CFC5DD3CF130EA0A10875E7B7C.node01#-#localhost#-#/outpatient#- #0#-#1203676448864 22/Fev/2008 10:34:10 org.apache.catalina.cluster.tcp.ReplicationValveresetDeltaRequest FINE: Cluster is standalone: reset Session Request Delta at context /outpatient 22/Fev/2008 10:34:38 org.apache.catalina.cluster.tcp.ReplicationValvecreatePrimaryIndicator FINE: Context /outpatient: Primarity of session 76CFC5DD3CF130EA0A10875E7B7C.node02 in request attribute org.apache.catalina.cluster.tcp.isPrimarySession is true. Our cluster setup: Cluster className=org.apache.catalina.cluster.tcp.SimpleTcpCluster doClusterLog=true clusterLogName=clusterlog manager.className= org.apache.catalina.cluster.session.DeltaManager manager.expireSessionsOnShutdown=false manager.notifyListenersOnReplication=false manager.notifySessionListenersOnReplication=false manager.sendAllSessions=false manager.sendAllSessionsSize=500 manager.sendAllSessionsWaitTime=20 Membership className= org.apache.catalina.cluster.mcast.McastService mcastAddr=228.0.0.4 mcastClusterDomain=d10 mcastPort=45564 mcastFrequency=1000 mcastDropTime=1000 recoveryCounter=10 recoveryEnabled=true recoverySleepTime=5000/ Receiver className= org.apache.catalina.cluster.tcp.ReplicationListener tcpListenAddress=auto tcpListenPort=9016 tcpSelectorTimeout=100 tcpThreadCount=6/ Sender className= org.apache.catalina.cluster.tcp.ReplicationTransmitter
