I just read through some of the tomcat source code for the Persistent Session Manager and it seems that there are three possibilities.
Session on the JVM heap lets call it the active session Session not in the JVM heap but in the persistent store this would be a swapped out session Session in the JVM heap and in the persistent store this would be a backed up session Now if anyone can shed some light on how often / when the persistent session manager decides to backup the sessions or what is considered an accessed session that would be highly appreciated. On Tue, Jan 25, 2011 at 3:32 AM, Adib <amsl...@gmail.com> wrote: > Hi, > > I am trying to understand the settings on the persistent session > manager on tomcat 6 and 7. It seems that the persistent session > manager is primarily meant for the purpose of swapping IDLE sessions > to persistent storage and then hope that they expire, I can see the > value of this given that many users abandon sites without logging out. > It also seems that the persisent manager is not designed to persist > every session at the end of every request so that at the start of > every request the session is read from the store and the end of the > request the session is written to store, is this understanding > correct. > > I have also been puzzling over the meanings of maxIdleSwap vs. > maxIdleBackup not sure why these two settings exist or what is > difference between them and the practical use case for them? It is > clear to me what the idle session is but what is meant by backup and > how is it different than a swap? > > Thanks > Adib > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
