Re: 5.5.17 cluster doesn't sync sessions on startup
Ok. It took a while, but I finally had the time to try this. The chunking of data looks promissing. The timeout is still 60 seconds in my config, but the servers have all the session in 1-3 seconds now. And I didn't receive any calls from the servicedesk yet. :-) Thanks for the info. I have another question about 'WARNING: overload existing session 69BA2674D292CE6C0EFBC6230F452C10', but wil ask it in a separate thread. Ronald. On Thu Sep 07 17:03:28 CEST 2006 Tomcat Users List users@tomcat.apache.org wrote: ok, in that case, there could so much session data that it takes longer than 60 seconds to retrive. you have two options 1. increase the transfer timeout 2. transfer data in chunks Cluster className=org.apache.catalina.cluster.tcp.SimpleTcpCluster manager.className=org.apache.catalina.cluster.session.DeltaManager manager.stateTransferTimeout=120 manager.sendAllSessions=false manager.sendAllSessionsSize=500 manager.sendAllSessionsWaitTime=20 I believe this is documented on the website Filip Ronald Klop wrote: No, one node is restarting, while the other three keep running. Ronald. On Wed Sep 06 19:18:14 CEST 2006 Tomcat Users List users@tomcat.apache.org wrote: are the nodes starting up simultanously, there is the risk of syncing not working if two nodes are starting at the same time as the cluster starts before the actual webapps are deployed. Filip Ronald Klop wrote: Hello, 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. When this happened on 5.0.x I got an ClassCastException, which explained why syncing failed. But on 5.5.17 I just get a timeout of 60 seconds. This is the start of the catalina.out. Sep 5, 2006 9:41:04 AM org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 Sep 5, 2006 9:41:04 AM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1399 ms Sep 5, 2006 9:41:04 AM org.apache.catalina.core.StandardService start INFO: Starting service Catalina Sep 5, 2006 9:41:04 AM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.5.17 Sep 5, 2006 9:41:04 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster start INFO: Cluster is about to start Sep 5, 2006 9:41:04 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterValves INFO: Add Default ClusterValves at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterListener INFO: Add Default ClusterListener at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterReceiver INFO: Add Default ClusterReceiver at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterSender INFO: Add Default ClusterSender at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SocketReplicationListener createServerSocket INFO: Open Socket at [10.0.10.55:8015] Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.ReplicationTransmitter start INFO: Start ClusterSender at cluster Catalina:type=Cluster with name Catalina:type=ClusterSender Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultMembershipService INFO: Add Default Membership Service at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.mcast.McastService start INFO: Sleeping for 4000 milliseconds to establish cluster membership Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster memberAdded INFO: Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://10.0.10.52:8015,catalina,10.0.10.52,8015, alive=67855063] Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.FastAsyncSocketSender checkThread INFO: Create sender [/10.0.10.52:8,015] queue thread to tcp background replication Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster memberAdded INFO: Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://10.0.10.73:8015,catalina,10.0.10.73,8015, alive=61675989] Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.FastAsyncSocketSender checkThread INFO: Create sender [/10.0.10.73:8,015] queue thread to tcp background replication Sep 5, 2006 9:41:06 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster memberAdded INFO: Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://10.0.10.53:8015,catalina,10.0.10.53,8015, alive=62452004] Sep 5, 2006 9:41:06 AM org.apache.catalina.cluster.tcp.FastAsyncSocketSender checkThread INFO: Create sender [/10.0.10.53:8,015] queue thread to tcp background
Re: 5.5.17 cluster doesn't sync sessions on startup
On Today at 1:13pm, RK=Ronald Klop [EMAIL PROTECTED] wrote: RK Ok. It took a while, but I finally had the time to try this. RK RK The chunking of data looks promissing. The timeout is still 60 seconds in my RK config, but the servers have all the session in 1-3 seconds now. And I RK didn't receive any calls from the servicedesk yet. :-) RK Hi Ronald, Enquiring minds want to konw what was the fix?. -- Haroon Rafique [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 5.5.17 cluster doesn't sync sessions on startup
I used: Cluster className=org.apache.catalina.cluster.tcp.SimpleTcpCluster manager.className=org.apache.catalina.cluster.session.DeltaManager manager.stateTransferTimeout=60 manager.sendAllSessions=false manager.sendAllSessionsSize=500 manager.sendAllSessionsWaitTime=20 in stead of: Cluster className=org.apache.catalina.cluster.tcp.SimpleTcpCluster/ on all my clusternodes as suggested by Filip. The fix is sendAllSessions=false in stead of true. This works better for me. See the tomcat docs for more info. Ronald. On Wed Nov 15 15:53:00 CET 2006 Tomcat Users List users@tomcat.apache.org wrote: On Today at 1:13pm, RK=Ronald Klop [EMAIL PROTECTED] wrote: RK Ok. It took a while, but I finally had the time to try this. RK RK The chunking of data looks promissing. The timeout is still 60 seconds in my RK config, but the servers have all the session in 1-3 seconds now. And I RK didn't receive any calls from the servicedesk yet. :-) RK Hi Ronald, Enquiring minds want to konw what was the fix?. -- Haroon Rafique [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 5.5.17 cluster doesn't sync sessions on startup
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]
Re: 5.5.17 cluster doesn't sync sessions on startup
Check that your server times are all synchronised. Ronald Klop wrote: Thanks for your anser. I'm going to look into this. I have some thoughts about this. Tomcat 5.0 synced in 0.3-3 seconds for the same amount of sessions. Our (about 3000-5000) sessions contain only one String 'userid' of max length 10, so that is 10 bytes of utf-16. Not very much. With class/object overhead I think 200KB over Gigabit ethernet. So more than 60 seconds in Tomcat 5.5.17 seems a bit weird. Of course this happens only in production where downtime or lost sessions is not appreciated. :-) It would be nice if Tomcat showed more information why the sync failed, but maybe it's hard to do that. Or maybe display how many sessions were synced before the timeout occurs. Ronald. On Thu Sep 07 17:03:28 CEST 2006 Tomcat Users List users@tomcat.apache.org wrote: ok, in that case, there could so much session data that it takes longer than 60 seconds to retrive. you have two options 1. increase the transfer timeout 2. transfer data in chunks Cluster className=org.apache.catalina.cluster.tcp.SimpleTcpCluster manager.className=org.apache.catalina.cluster.session.DeltaManager manager.stateTransferTimeout=120 manager.sendAllSessions=false manager.sendAllSessionsSize=500 manager.sendAllSessionsWaitTime=20 I believe this is documented on the website Filip Ronald Klop wrote: No, one node is restarting, while the other three keep running. Ronald. On Wed Sep 06 19:18:14 CEST 2006 Tomcat Users List users@tomcat.apache.org wrote: are the nodes starting up simultanously, there is the risk of syncing not working if two nodes are starting at the same time as the cluster starts before the actual webapps are deployed. Filip Ronald Klop wrote: Hello, 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. When this happened on 5.0.x I got an ClassCastException, which explained why syncing failed. But on 5.5.17 I just get a timeout of 60 seconds. This is the start of the catalina.out. Sep 5, 2006 9:41:04 AM org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 Sep 5, 2006 9:41:04 AM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1399 ms Sep 5, 2006 9:41:04 AM org.apache.catalina.core.StandardService start INFO: Starting service Catalina Sep 5, 2006 9:41:04 AM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.5.17 Sep 5, 2006 9:41:04 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster start INFO: Cluster is about to start Sep 5, 2006 9:41:04 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterValves INFO: Add Default ClusterValves at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterListener INFO: Add Default ClusterListener at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterReceiver INFO: Add Default ClusterReceiver at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterSender INFO: Add Default ClusterSender at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SocketReplicationListener createServerSocket INFO: Open Socket at [10.0.10.55:8015] Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.ReplicationTransmitter start INFO: Start ClusterSender at cluster Catalina:type=Cluster with name Catalina:type=ClusterSender Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultMembershipService INFO: Add Default Membership Service at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.mcast.McastService start INFO: Sleeping for 4000 milliseconds to establish cluster membership Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster memberAdded INFO: Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://10.0.10.52:8015,catalina,10.0.10.52,8015, alive=67855063] Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.FastAsyncSocketSender checkThread INFO: Create sender [/10.0.10.52:8,015] queue thread to tcp background replication Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster memberAdded INFO: Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://10.0.10.73:8015,catalina,10.0.10.73,8015, alive=61675989] Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.FastAsyncSocketSender checkThread INFO: Create sender [/10.0.10.73:8,015] queue thread to tcp background replication
Re: 5.5.17 cluster doesn't sync sessions on startup
Hi Ronald, 5000 small sessions are really sync very fast with tomcat 5.5.17 also. I have test this and it works. Tomorrow I have more time to simulate your case. regards peter Am 07.09.2006 um 20:33 schrieb Ronald Klop: Thanks for your anser. I'm going to look into this. I have some thoughts about this. Tomcat 5.0 synced in 0.3-3 seconds for the same amount of sessions. Our (about 3000-5000) sessions contain only one String 'userid' of max length 10, so that is 10 bytes of utf-16. Not very much. With class/object overhead I think 200KB over Gigabit ethernet. So more than 60 seconds in Tomcat 5.5.17 seems a bit weird. Of course this happens only in production where downtime or lost sessions is not appreciated. :-) Why the node is restart or started? Are you sure you don't have a network problem? The message overload meants that GET_ALL_SESSION message is received very sort after timeout. Sep 5, 2006 9:42:14 AM org.apache.catalina.cluster.session.DeltaManager waitForSendAllSessions SEVERE: Manager [localhost]: No session state send at 9/5/06 9:41 AM received, timing out after 60,033 ms. Sep 5, 2006 9:42:16 AM org.apache.catalina.cluster.session.DeltaManager deserializeSessions WARNING: overload existing session 5D8486234FCD60EF7A59CBAED66E20EA It would be nice if Tomcat showed more information why the sync failed, but maybe it's hard to do that. Or maybe display how many sessions were synced before the timeout occurs. Which information you want see? Look at docs and search for clusterlog, Set trace loglevel for the cluster classes. Ronald. On Thu Sep 07 17:03:28 CEST 2006 Tomcat Users List users@tomcat.apache.org wrote: ok, in that case, there could so much session data that it takes longer than 60 seconds to retrive. you have two options 1. increase the transfer timeout 2. transfer data in chunks Cluster className=org.apache.catalina.cluster.tcp.SimpleTcpCluster manager.className=org.apache.catalina.cluster.session.DeltaManager manager.stateTransferTimeout=120 manager.sendAllSessions=false manager.sendAllSessionsSize=500 manager.sendAllSessionsWaitTime=20 I believe this is documented on the website Filip Ronald Klop wrote: No, one node is restarting, while the other three keep running. Ronald. On Wed Sep 06 19:18:14 CEST 2006 Tomcat Users List users@tomcat.apache.org wrote: are the nodes starting up simultanously, there is the risk of syncing not working if two nodes are starting at the same time as the cluster starts before the actual webapps are deployed. Filip Ronald Klop wrote: Hello, 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. When this happened on 5.0.x I got an ClassCastException, which explained why syncing failed. But on 5.5.17 I just get a timeout of 60 seconds. This is the start of the catalina.out. Sep 5, 2006 9:41:04 AM org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 Sep 5, 2006 9:41:04 AM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1399 ms Sep 5, 2006 9:41:04 AM org.apache.catalina.core.StandardService start INFO: Starting service Catalina Sep 5, 2006 9:41:04 AM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.5.17 Sep 5, 2006 9:41:04 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster start INFO: Cluster is about to start Sep 5, 2006 9:41:04 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterValves INFO: Add Default ClusterValves at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterListener INFO: Add Default ClusterListener at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterReceiver INFO: Add Default ClusterReceiver at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterSender INFO: Add Default ClusterSender at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SocketReplicationListener createServerSocket INFO: Open Socket at [10.0.10.55:8015] Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.ReplicationTransmitter start INFO: Start ClusterSender at cluster Catalina:type=Cluster with name Catalina:type=ClusterSender Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultMembershipService INFO: Add Default Membership Service at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.mcast.McastService start INFO: Sleeping for 4000 milliseconds to establish cluster membership Sep 5, 2006 9:41:05 AM
5.5.17 cluster doesn't sync sessions on startup
Hello, 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. When this happened on 5.0.x I got an ClassCastException, which explained why syncing failed. But on 5.5.17 I just get a timeout of 60 seconds. This is the start of the catalina.out. Sep 5, 2006 9:41:04 AM org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 Sep 5, 2006 9:41:04 AM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1399 ms Sep 5, 2006 9:41:04 AM org.apache.catalina.core.StandardService start INFO: Starting service Catalina Sep 5, 2006 9:41:04 AM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.5.17 Sep 5, 2006 9:41:04 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster start INFO: Cluster is about to start Sep 5, 2006 9:41:04 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterValves INFO: Add Default ClusterValves at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterListener INFO: Add Default ClusterListener at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterReceiver INFO: Add Default ClusterReceiver at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterSender INFO: Add Default ClusterSender at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SocketReplicationListener createServerSocket INFO: Open Socket at [10.0.10.55:8015] Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.ReplicationTransmitter start INFO: Start ClusterSender at cluster Catalina:type=Cluster with name Catalina:type=ClusterSender Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultMembershipService INFO: Add Default Membership Service at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.mcast.McastService start INFO: Sleeping for 4000 milliseconds to establish cluster membership Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster memberAdded INFO: Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://10.0.10.52:8015,catalina,10.0.10.52,8015, alive=67855063] Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.FastAsyncSocketSender checkThread INFO: Create sender [/10.0.10.52:8,015] queue thread to tcp background replication Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster memberAdded INFO: Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://10.0.10.73:8015,catalina,10.0.10.73,8015, alive=61675989] Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.FastAsyncSocketSender checkThread INFO: Create sender [/10.0.10.73:8,015] queue thread to tcp background replication Sep 5, 2006 9:41:06 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster memberAdded INFO: Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://10.0.10.53:8015,catalina,10.0.10.53,8015, alive=62452004] Sep 5, 2006 9:41:06 AM org.apache.catalina.cluster.tcp.FastAsyncSocketSender checkThread INFO: Create sender [/10.0.10.53:8,015] queue thread to tcp background replication Sep 5, 2006 9:41:09 AM org.apache.catalina.cluster.mcast.McastService registerMBean INFO: membership mbean registered (Catalina:type=ClusterMembership) Sep 5, 2006 9:41:09 AM org.apache.catalina.core.StandardHost start INFO: XML validation disabled Sep 5, 2006 9:41:09 AM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive ROOT.war Sep 5, 2006 9:41:09 AM org.apache.catalina.cluster.session.ClusterSessionListener messageReceived SEVERE: Context manager doesn't exist:localhost Sep 5, 2006 9:41:09 AM org.apache.catalina.cluster.session.ClusterSessionListener messageReceived SEVERE: Context manager doesn't exist:localhost Sep 5, 2006 9:41:09 AM org.apache.catalina.cluster.session.ClusterSessionListener messageReceived SEVERE: Context manager doesn't exist:localhost Sep 5, 2006 9:41:09 AM org.apache.catalina.cluster.session.ClusterSessionListener messageReceived SEVERE: Context manager doesn't exist:localhost Sep 5, 2006 9:41:09 AM org.apache.catalina.cluster.session.ClusterSessionListener messageReceived SEVERE: Context manager doesn't exist:localhost Sep 5, 2006 9:41:09 AM org.apache.catalina.cluster.session.ClusterSessionListener messageReceived SEVERE: Context manager doesn't exist:localhost Sep 5, 2006 9:41:10 AM org.apache.catalina.cluster.session.ClusterSessionListener messageReceived SEVERE: Context manager doesn't exist:localhost Sep 5, 2006 9:41:10 AM org.apache.catalina.cluster.session.ClusterSessionListener messageReceived SEVERE: Context manager doesn't exist:localhost Sep 5, 2006 9:41:10 AM
Re: 5.5.17 cluster doesn't sync sessions on startup
are the nodes starting up simultanously, there is the risk of syncing not working if two nodes are starting at the same time as the cluster starts before the actual webapps are deployed. Filip Ronald Klop wrote: Hello, 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. When this happened on 5.0.x I got an ClassCastException, which explained why syncing failed. But on 5.5.17 I just get a timeout of 60 seconds. This is the start of the catalina.out. Sep 5, 2006 9:41:04 AM org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 Sep 5, 2006 9:41:04 AM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1399 ms Sep 5, 2006 9:41:04 AM org.apache.catalina.core.StandardService start INFO: Starting service Catalina Sep 5, 2006 9:41:04 AM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.5.17 Sep 5, 2006 9:41:04 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster start INFO: Cluster is about to start Sep 5, 2006 9:41:04 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterValves INFO: Add Default ClusterValves at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterListener INFO: Add Default ClusterListener at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterReceiver INFO: Add Default ClusterReceiver at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterSender INFO: Add Default ClusterSender at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SocketReplicationListener createServerSocket INFO: Open Socket at [10.0.10.55:8015] Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.ReplicationTransmitter start INFO: Start ClusterSender at cluster Catalina:type=Cluster with name Catalina:type=ClusterSender Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultMembershipService INFO: Add Default Membership Service at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.mcast.McastService start INFO: Sleeping for 4000 milliseconds to establish cluster membership Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster memberAdded INFO: Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://10.0.10.52:8015,catalina,10.0.10.52,8015, alive=67855063] Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.FastAsyncSocketSender checkThread INFO: Create sender [/10.0.10.52:8,015] queue thread to tcp background replication Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster memberAdded INFO: Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://10.0.10.73:8015,catalina,10.0.10.73,8015, alive=61675989] Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.FastAsyncSocketSender checkThread INFO: Create sender [/10.0.10.73:8,015] queue thread to tcp background replication Sep 5, 2006 9:41:06 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster memberAdded INFO: Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://10.0.10.53:8015,catalina,10.0.10.53,8015, alive=62452004] Sep 5, 2006 9:41:06 AM org.apache.catalina.cluster.tcp.FastAsyncSocketSender checkThread INFO: Create sender [/10.0.10.53:8,015] queue thread to tcp background replication Sep 5, 2006 9:41:09 AM org.apache.catalina.cluster.mcast.McastService registerMBean INFO: membership mbean registered (Catalina:type=ClusterMembership) Sep 5, 2006 9:41:09 AM org.apache.catalina.core.StandardHost start INFO: XML validation disabled Sep 5, 2006 9:41:09 AM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive ROOT.war Sep 5, 2006 9:41:09 AM org.apache.catalina.cluster.session.ClusterSessionListener messageReceived SEVERE: Context manager doesn't exist:localhost Sep 5, 2006 9:41:09 AM org.apache.catalina.cluster.session.ClusterSessionListener messageReceived SEVERE: Context manager doesn't exist:localhost Sep 5, 2006 9:41:09 AM org.apache.catalina.cluster.session.ClusterSessionListener messageReceived SEVERE: Context manager doesn't exist:localhost Sep 5, 2006 9:41:09 AM org.apache.catalina.cluster.session.ClusterSessionListener messageReceived SEVERE: Context manager doesn't exist:localhost Sep 5, 2006 9:41:09 AM org.apache.catalina.cluster.session.ClusterSessionListener messageReceived SEVERE: Context manager doesn't exist:localhost Sep 5, 2006 9:41:09 AM org.apache.catalina.cluster.session.ClusterSessionListener messageReceived SEVERE: Context manager doesn't exist:localhost Sep 5, 2006 9:41:10 AM org.apache.catalina.cluster.session.ClusterSessionListener messageReceived
Re: 5.5.17 cluster doesn't sync sessions on startup
No, one node is restarting, while the other three keep running. Ronald. On Wed Sep 06 19:18:14 CEST 2006 Tomcat Users List users@tomcat.apache.org wrote: are the nodes starting up simultanously, there is the risk of syncing not working if two nodes are starting at the same time as the cluster starts before the actual webapps are deployed. Filip Ronald Klop wrote: Hello, 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. When this happened on 5.0.x I got an ClassCastException, which explained why syncing failed. But on 5.5.17 I just get a timeout of 60 seconds. This is the start of the catalina.out. Sep 5, 2006 9:41:04 AM org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 Sep 5, 2006 9:41:04 AM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1399 ms Sep 5, 2006 9:41:04 AM org.apache.catalina.core.StandardService start INFO: Starting service Catalina Sep 5, 2006 9:41:04 AM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.5.17 Sep 5, 2006 9:41:04 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster start INFO: Cluster is about to start Sep 5, 2006 9:41:04 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterValves INFO: Add Default ClusterValves at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterListener INFO: Add Default ClusterListener at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterReceiver INFO: Add Default ClusterReceiver at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultClusterSender INFO: Add Default ClusterSender at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SocketReplicationListener createServerSocket INFO: Open Socket at [10.0.10.55:8015] Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.ReplicationTransmitter start INFO: Start ClusterSender at cluster Catalina:type=Cluster with name Catalina:type=ClusterSender Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster createDefaultMembershipService INFO: Add Default Membership Service at cluster Catalina Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.mcast.McastService start INFO: Sleeping for 4000 milliseconds to establish cluster membership Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster memberAdded INFO: Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://10.0.10.52:8015,catalina,10.0.10.52,8015, alive=67855063] Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.FastAsyncSocketSender checkThread INFO: Create sender [/10.0.10.52:8,015] queue thread to tcp background replication Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster memberAdded INFO: Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://10.0.10.73:8015,catalina,10.0.10.73,8015, alive=61675989] Sep 5, 2006 9:41:05 AM org.apache.catalina.cluster.tcp.FastAsyncSocketSender checkThread INFO: Create sender [/10.0.10.73:8,015] queue thread to tcp background replication Sep 5, 2006 9:41:06 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster memberAdded INFO: Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://10.0.10.53:8015,catalina,10.0.10.53,8015, alive=62452004] Sep 5, 2006 9:41:06 AM org.apache.catalina.cluster.tcp.FastAsyncSocketSender checkThread INFO: Create sender [/10.0.10.53:8,015] queue thread to tcp background replication Sep 5, 2006 9:41:09 AM org.apache.catalina.cluster.mcast.McastService registerMBean INFO: membership mbean registered (Catalina:type=ClusterMembership) Sep 5, 2006 9:41:09 AM org.apache.catalina.core.StandardHost start INFO: XML validation disabled Sep 5, 2006 9:41:09 AM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive ROOT.war Sep 5, 2006 9:41:09 AM org.apache.catalina.cluster.session.ClusterSessionListener messageReceived SEVERE: Context manager doesn't exist:localhost Sep 5, 2006 9:41:09 AM org.apache.catalina.cluster.session.ClusterSessionListener messageReceived SEVERE: Context manager doesn't exist:localhost Sep 5, 2006 9:41:09 AM org.apache.catalina.cluster.session.ClusterSessionListener messageReceived SEVERE: Context manager doesn't exist:localhost Sep 5, 2006 9:41:09 AM org.apache.catalina.cluster.session.ClusterSessionListener messageReceived SEVERE: Context manager doesn't exist:localhost Sep 5, 2006 9:41:09 AM org.apache.catalina.cluster.session.ClusterSessionListener messageReceived SEVERE: Context manager doesn't
