Thanks for the reply Martin. However, I know about Serializable interface and Session Timeouts.
I am using CAS (which is a huge Java open-source Single Sign-On web application). I do not want to tamper with the original code. What confuses me is, why do the CAS session objects remain in the session even when I made the necessary changes to the Tomcat config files and restarted Tomcat. Thank you! Kristin On Nov 14, 2007 5:46 PM, Martin Gainty <[EMAIL PROTECTED]> wrote: > "implements serializable" > > Read this important article on implements Serializable from 2000 > http://java.sun.com/developer/TechTips/2000/tt0229.html > > And this article on Session Serialization and Session.timeout > http://java.sys-con.com/read/37330.htm > > M-- > > ----- Original Message ----- > From: "Kristin Coles" <[EMAIL PROTECTED]> > To: <users@tomcat.apache.org> > Sent: Wednesday, November 14, 2007 7:22 PM > Subject: How to disable Session Persistence in Tomcat 5.5.9 > > > > Hi guys, > > > > I know that there have been quite a few threads on this list that > > relate to the same subject. I have tried the following advice but none > > helped. > > > > # Tomcat\conf\context.xml > > <Context> > > <WatchedResource>WEB-INF/web.xml</WatchedResource> > > <Manager pathname="" /> > > </Context> > > > > # Tomcat\conf\server.xml (version 1) > > <Host name="cas" appBase="webapps\cas" > > unpackWARs="true" autoDeploy="true" > > xmlValidation="false" xmlNamespaceAware="false" > > expireSessionsOnShutdown="true"> > > <Context path="" docBase=""> > > <Manager className="org.apache.catalina.session.PersistentManager" > > debug="0" > > saveOnRestart="false" > > maxActiveSessions="-1" > > minIdleSwap="-1" > > maxIdleSwap="-1" > > maxIdleBackup="-1"> > > <Store className="org.apache.catalina.session.FileStore" > > directory="logs/sessions" /> > > </Manager> > > </Context> > > </Host> > > > > # Tomcat\conf\server.xml (version 2) > > <Host name="cas" appBase="webapps\cas" > > unpackWARs="true" autoDeploy="true" > > xmlValidation="false" xmlNamespaceAware="false" > > expireSessionsOnShutdown="true"> > > <Context path="" docBase=""> > > <Manager className="org.apache.catalina.session.StandardManager" > > debug="0" pathname =""> > > </Manager> > > </Context> > > </Host> > > > > I have deployed and configured CAS (Central Authentication Service for > > Single Sign-On) as as web application on Tomcat. However, while using > > CAS, I've found that the user who was logged in before the Tomcat > > restart, is still logged in after the Tomcat restart. > > > > Can anyone here please help resolve this issue!!! > > > > Thank you, > > Kristin > > > > --------------------------------------------------------------------- > > To start a new topic, e-mail: users@tomcat.apache.org > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
