You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Ronald Klop <ro...@base.nl> on 2006/11/15 13:13:23 UTC
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 <us...@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
> > <us...@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 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 >
> >> 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:11 AM >
> >> org.apache.catalina.cluster.session.ClusterSessionListener >
> >> messageReceived
> >> > SEVERE: Context manager doesn't exist:localhost
> >> > Sep 5, 2006 9:41:11 AM >
> >> org.apache.catalina.cluster.session.ClusterSessionListener >
> >> messageReceived
> >> > SEVERE: Context manager doesn't exist:localhost
> >> > Sep 5, 2006 9:41:11 AM >
> >> org.apache.catalina.cluster.session.ClusterSessionListener >
> >> messageReceived
> >> > SEVERE: Context manager doesn't exist:localhost
> >> > Sep 5, 2006 9:41:11 AM >
> >> org.apache.catalina.cluster.session.ClusterSessionListener >
> >> messageReceived
> >> > SEVERE: Context manager doesn't exist:localhost
> >> > Sep 5, 2006 9:41:11 AM >
> >> org.apache.catalina.cluster.session.ClusterSessionListener >
> >> messageReceived
> >> > SEVERE: Context manager doesn't exist:localhost
> >> > Sep 5, 2006 9:41:12 AM >
> >> org.apache.catalina.cluster.session.ClusterSessionListener >
> >> messageReceived
> >> > SEVERE: Context manager doesn't exist:localhost
> >> > Sep 5, 2006 9:41:12 AM >
> >> org.apache.catalina.cluster.session.ClusterSessionListener >
> >> messageReceived
> >> > SEVERE: Context manager doesn't exist:localhost
> >> > Sep 5, 2006 9:41:12 AM >
> >> org.apache.catalina.cluster.session.ClusterSessionListener >
> >> messageReceived
> >> > SEVERE: Context manager doesn't exist:localhost
> >> > Sep 5, 2006 9:41:12 AM >
> >> org.apache.catalina.cluster.session.ClusterSessionListener >
> >> messageReceived
> >> > SEVERE: Context manager doesn't exist:localhost
> >> > Sep 5, 2006 9:41:14 AM >
> >> org.apache.catalina.cluster.session.ClusterSessionListener >
> >> messageReceived
> >> > SEVERE: Context manager doesn't exist:localhost
> >> > Sep 5, 2006 9:41:14 AM >
> >> org.apache.catalina.cluster.session.DeltaManager start
> >> > INFO: Register manager to cluster element Engine with name Catalina
> >> > Sep 5, 2006 9:41:14 AM >
> >> org.apache.catalina.cluster.session.DeltaManager start
> >> > INFO: Starting clustering manager at
> >> > Sep 5, 2006 9:41:14 AM >
> >> org.apache.catalina.cluster.session.DeltaManager getAllClusterSessions
> >> > WARNING: Manager [localhost], requesting session state from >
> >> org.apache.catalina.cluster.mcast.McastMember[tcp://10.0.10.52:8015,catalina,10.0.10.52,8015,
> >> > alive=67863169]. This operation will timeout if no session state
> >> has > been received within 60 seconds.
> >> > 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
> >> > Sep 5, 2006 9:42:40 AM org.apache.coyote.http11.Http11BaseProtocol
> >> start
> >> > INFO: Starting Coyote HTTP/1.1 on http-8080
> >> > Sep 5, 2006 9:42:41 AM org.apache.catalina.storeconfig.StoreLoader
> >> load
> >> > INFO: Find registry server-registry.xml at classpath resource
> >> > Sep 5, 2006 9:42:42 AM org.apache.catalina.startup.Catalina start
> >> > INFO: Server startup in 97508 ms
> >> >
> >> > This is the server.xml.
> >> >
> >> > <Server port="8005" shutdown="SHUTDOWN" debug="0">
> >> > <Listener >
> >> className="org.apache.catalina.mbeans.ServerLifecycleListener" />
> >> > <Listener >
> >> className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
> >> > />
> >> > <Listener >
> >> className="org.apache.catalina.storeconfig.StoreConfigLifecycleListener"/>
> >> >
> >> >
> >> > <GlobalNamingResources>
> >> >
> >> > <!-- Editable user database that can also be used by
> >> > UserDatabaseRealm to authenticate users -->
> >> > <Resource name="UserDatabase" auth="Container"
> >> > type="org.apache.catalina.UserDatabase"
> >> > description="User database that can be updated and saved"
> >> > factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
> >> > pathname="conf/tomcat-users.xml" />
> >> >
> >> > </GlobalNamingResources>
> >> >
> >> > <!-- Define the Tomcat Stand-Alone Service -->
> >> > <Service name="Catalina">
> >> > <!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
> >> > <Connector port="8080" maxHttpHeaderSize="8192"
> >> > maxThreads="300" minSpareThreads="25" maxSpareThreads="75"
> >> > enableLookups="false" redirectPort="8443" > acceptCount="1024"
> >> > connectionTimeout="20000" disableUploadTimeout="true"
> >> > compression="on"
> >> > >
> >> compressableMimeTypes="text/html,text/xml,text/plain,text/javascript,text/css"/>
> >> >
> >> >
> >> > <!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
> >> > <!--
> >> > <Connector port="8009"
> >> > enableLookups="false" redirectPort="8443" debug="0"
> >> > protocol="AJP/1.3" />
> >> > -->
> >> >
> >> > <Engine name="Catalina" defaultHost="localhost">
> >> >
> >> > <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
> >> > resourceName="UserDatabase"/>
> >> >
> >> > <Cluster >
> >> className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"/>
> >> >
> >> > <Host name="localhost"
> >> > appBase="/usr/local/crm-CRM21/deployed"
> >> > unpackWARs="true" autoDeploy="false" reloadable="false"
> >> > usePooling="false"
> >> > xmlValidation="false" xmlNamespaceAware="true">
> >> > </Host>
> >> > <!--
> >> > <Host name="rc.realworks.nl"
> >> > appBase="/usr/local/crm-RC/deployed"
> >> > unpackWARs="true" autoDeploy="false" reloadable="false"
> >> > usePooling="false"
> >> > xmlValidation="false" xmlNamespaceAware="true">
> >> > </Host>
> >> > -->
> >> >
> >> > </Engine>
> >> > </Service>
> >> > </Server>
> >> >
> >> > Does this make sense to anybody? Can I provide more info?
> >> >
> >> > Ronald.
> >> >
> >> ------------------------------------------------------------------------
> >> >
> >> > No virus found in this incoming message.
> >> > Checked by AVG Free Edition.
> >> > Version: 7.1.405 / Virus Database: 268.11.7/438 - Release Date:
> >> 9/5/2006
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To start a new topic, e-mail: users@tomcat.apache.org
> >> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> >> For additional commands, e-mail: users-help@tomcat.apache.org
> >>
> >
> > ------------------------------------------------------------------------
> >
> > No virus found in this incoming message.
> > Checked by AVG Free Edition.
> > Version: 7.1.405 / Virus Database: 268.11.7/438 - Release Date: 9/5/2006
> >
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
Re: 5.5.17 cluster doesn't sync sessions on startup
Posted by Ronald Klop <ro...@base.nl>.
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 <us...@tomcat.apache.org> wrote:
> On Today at 1:13pm, RK=>Ronald Klop <ro...@base.nl> 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
> <ha...@utoronto.ca>
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
Re: 5.5.17 cluster doesn't sync sessions on startup
Posted by Haroon Rafique <ha...@utoronto.ca>.
On Today at 1:13pm, RK=>Ronald Klop <ro...@base.nl> 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
<ha...@utoronto.ca>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org