On 9/6/06, Ronald Klop <[EMAIL PROTECTED]> wrote:
We are running a 4-node cluster of 5.5.17. Sometimes java or tomcat
crashes and we restart it automaticly. With 5.0.x this was ok, but
with 5.5.x it doesn't sync session on startup often.
Ronald, I am seeing nearly the exact same issue/errors with 5.5.20 in a
2-tomcat cluster.
When shutting down, Tomcat #1 logs:
2006-10-20 03:31:03,014 WARN : DataSender: Message transfered: Sender
cant disconnect from [{0}:{1,number,integer}]
When starting back up it logs:
2006-10-20 03:31:05,565 INFO : SocketReplicationListener: Open Socket
at [10.1.1.5:8015]
2006-10-20 03:31:05,588 ERROR: ClusterListener: Context manager doesn't exist:
2006-10-20 03:31:05,589 ERROR: ClusterListener: Context manager doesn't exist:
That second line repeats many, many times for about 5 seconds.
Then it says:
2006-10-20 03:31:10,079 INFO : DeltaManager: Starting clustering manager at
2006-10-20 03:31:10,083 WARN : DeltaManager: Manager [], requesting
session state from
org.apache.catalina.cluster.mcast.McastMember[tcp://10.1.1.6:8015,catalina,10.1.1.6,8015,
alive=86340978]. This operation will timeout if no session state has
been received within 60 seconds.
2006-10-20 03:32:10,163 ERROR: DeltaManager: Manager []: No session
state send at 20/10/06 03:31 received, timing out after 60,084 ms.
2006-10-20 03:32:10,164 WARN : DeltaManager: Manager []: Drop message
SESSION-GET-ALL inside GET_ALL_SESSIONS sync phase start date 20/10/06
03:31 message date 20/10/06 03:32
Meanwhile, Tomcat #2 repeatedly logs for about 5 seconds (IE, appx
until Tomcat #1 stops saying that the Context manager doesn't exist):
2006-10-20 03:31:03,531 WARN : FastAsyncSocketSender: Unable to
asynchronously send session with
id=[D24CF15CCCD87889679A9C84F39E533D.web2-1161220503024] -
message will be ignored.
java.net.SocketException: Connection reset
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:96)
at java.net.SocketOutputStream.write(SocketOutputStream.java:124)
at
org.apache.catalina.cluster.tcp.DataSender.writeData(DataSender.java:882)
at
org.apache.catalina.cluster.tcp.DataSender.pushMessage(DataSender.java:821)
at
org.apache.catalina.cluster.tcp.FastAsyncSocketSender$FastQueueThread.pushQueuedMessages(FastAsyncSocketSender.java:476)
at
org.apache.catalina.cluster.tcp.FastAsyncSocketSender$FastQueueThread.run(FastAsyncSocketSender.java:442)
Part of my problem I think is that I shut down Tomcat #2 before Tomcat #1
comes all the way back up as I normally restart Tomcat #2 1 minute after
Tomcat #2. I've separated the restart times by 4 minutes now, hopefully
they will sync up tomorrow.
Occasionally if I restart one of them for maintenance, it won't sync up
either, but usually a second restart gets it going again.
My cluster config looks like this:
<Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster">
<Valve className="org.apache.catalina.cluster.tcp.ReplicationValve"
filter=".*\.gif;.*\.js;.*\.jpg;.*\.png;.*\.htm;.*\.html;.*\.css;.*\.txt;"/>
<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.JvmRouteSessionIDBinderListener"/>
</Cluster>
-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]
