Tomcat Clustering - Replicated Sessions

[Laura Haverkamp <lh...@gmail.com>]

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
collection.

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.

Thanks.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

Re: Tomcat Clustering - Replicated Sessions

[Peter Rossbach <pr...@objektpark.de>]

Hey,

you have install my cluster patch for 5.5.9?
http://issues.apache.org/bugzilla/show_bug.cgi?id=34389

I  used very heavy  the new fastasyncqueue mode without memory problems

Every minute the sessions controlled for timeout. Look with an JMX 
Console that the manager active session count is reduced.
Every expire message are transfered to all backup nodes.

Peter


Laura Haverkamp schrieb:

>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
>collection.
>
>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.
>
>Thanks.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
>
>
>  
>





---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org