Hi David,

I have also made a test with two cluster nodes. Is node2 under load as node1 is started the message are normal. Cluster is starts first and receive message, but the application starts later. As application is startet at node1 the manager request node2 for current sessions. All message that received before the sync is complete are dropped. All message has a timestamp and only message dropped before the GET_ALL_SESSION message are created.

At next release 5.5.26 the sessionCounter is also set correct after restart. At my test all sessions are correct load
after restart.

Peter

PS: My Cluster Config:

<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="224.0.0.4"
                           mcastPort="${mcast.port.prefix}7"
                           mcastFrequency="1000"
                           mcastDropTime="30000"/>
<Receiver className="org.apache.catalina.cluster.tcp.ReplicationListener"
                           tcpListenAddress="auto"
                           tcpListenPort="${port.prefix}7"
                           tcpSelectorTimeout="100"
                           tcpThreadCount="6" />
<Sender className="org.apache.catalina.cluster.tcp.ReplicationTransmitter"
                           replicationMode="fastasyncqueue"
                           recoverTimeout="5000"
                           recoverCounter="6"
                           doTransmitterProcessingStats="true"
                           doProcessingStats="true"
                           doWaitAckStats="true"
                           queueTimeWait="true"
                           queueDoStats="true"
                           queueCheckLock="true"
                           ackTimeout="15000"
                           waitForAck="true"
                           keepAliveTimeout="80000"
                           keepAliveMaxRequestCount="-1"/>
<Valve className="org.apache.catalina.cluster.tcp.ReplicationValve" filter=".*\.gif;.* \.js;.*\.css;.*\.png;.*\.jpeg;.*\.jpg;.*\.htm;.*\.html;.*\.txt;"
                                    primaryIndicator="true" />
<Valve className="org.apache.catalina.cluster.session.JvmRouteBinderValve"
                                             enabled="true" />     
<ClusterListener className="org.apache.catalina.cluster.session.ClusterSessionListener" / > <ClusterListener className="org.apache.catalina.cluster.session.JvmRouteSessionIDBinderLi stener" />
              </Cluster>


Am 17.01.2008 um 09:24 schrieb David Rees:

On Jan 17, 2008 12:16 AM, Peter Rossbach <[EMAIL PROTECTED]> wrote:
you can't restart your nodes so quickly. As you shutdown one node you
must wait 30-45 sec before next restart. Don't restart both nodes at same time.

I am waiting at 4 minutes before restarting node 2 before restarting
node 1, so that is not the problem in this case.

The sequence goes like this:

04:30: Shut down node 1, it gets restarted automatically immediately
after it has completely shut down (typically within 10 seconds).
04:34: Shut down node 2, it gets restarted automatically immediately
after it has completely shut down (typically within 10 seconds).

-Dave

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to