Bug 42691 - sessions increase timeout as cluster members join
sessions increase timeout as cluster members join
Status: RESOLVED FIXED
Product: Tomcat 5
Classification: Unclassified
Component: Catalina:Cluster
5.5.23
All All
: P2 normal (vote)
: ---
Assigned To: Tomcat Developers Mailing List
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2007-06-18 07:34 UTC by Casey Lucas
Modified: 2007-08-14 01:06 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Casey Lucas 2007-06-18 07:34:26 UTC
This is probably not a big problem for most users of session replication. 
However for us it was worth fixing.

In our environment we commonly perform rolling software upgrades across our web
site.  While testing replication, we noticed that as we shutdown and restarted
nodes, the session counts would continually grow.  Basically, we found that as
sessions are transfered at startup time, the local access time is set to the
transfer time.  Code comments imply that this is done to prevent incorrect node
time synchronization problems.  However, it also simulates activity for old
sessions that are about to expire.  Under load, if you restart nodes enough,
your session count will keep growing and growing.

We changed the current behavior to keep existing session access times by
commenting out the call to session.access() in DeltaManager.deserializeSessions
(line 782 in svn revision 548361)
Comment 1 Peter Rossbach 2007-08-14 01:06:03 UTC
Thanks to find this ugly behaviour :-)
Peter