tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Laura Haverkamp <>
Subject Tomcat Clustering - Replicated Sessions
Date Mon, 02 May 2005 13:22:12 GMT
According to the Tomcat (5.5.9) documentation after a sessions has
reached a certian period of inactivity it expires.  However my
question is when is this expired session marked by the JVM for garbage

The reason I ask is that our application has an interesting problem. 
If we start up a single server (configured for a cluster) and have the
application run memory looks good, CPU is good, response time is good.

However when we start up the 2nd clustered instance after a day or two
both servers start showing up with OutOfMemory errors.  The only new
item introduced is that we are now replicating sessions between the
applications.  We changed the replication mode to asynchronous after
having performance problems using pooled.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message