Howdy, >The following is my application context file: > ><Context displayName="Nokia Web Guidelines (NWG)" docBase="nwg" >path="/nwg"> > <Manager saveOnRestart="false"/> > <ResourceLink name="rcfDS" global="jdbc/rcfDS" >type="javax.sql.DataSource"/> ></Context>
As the manager doc states, saveOnRestart is a feature of the PersistentManager, not the StandardManager. So you need to specify the manager implementation class as PersistentManager (or a custom extension of it). That in turn requires a Store element defining the session data store. >An unrelated suggestion for Tomcat: This session persistence capability is >awesome... in principle. If I had known about it before code-freeze I >would have ensured all my session objects were serializable and taken >advantage of it. Persistence could be very valuable to many people, and >it would be very beneficial if the docs had the "serializable session >object" requirement showing somewhere that is VERY visible. Where would you suggest putting this extra documentation? The origin of this is from the servlet spec, SRV.7.7.2, which suggests making your attributes serialized. Yoav Shapira > >b. > >-----Original Message----- >From: ext Shapira, Yoav [mailto:[EMAIL PROTECTED] >Sent: Wednesday, January 14, 2004 12:02 PM >To: Tomcat Users List >Subject: RE: Manager - STOP application fails to stop session!!! > > > >Howdy, ><sigh> >http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/manager.html ></sigh> > >Yoav Shapira >Millennium ChemInformatics > > >>-----Original Message----- >>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >>Sent: Wednesday, January 14, 2004 12:54 PM >>To: [EMAIL PROTECTED] >>Subject: RE: Manager - STOP application fails to stop session!!! >> >>Disabling session persistence was my first choice. But I have been >unable >>to find any clear information as to how to accomplish it. >> >>I imagine there is something that I can put on server.xml (or if I am >>lucky, in the application context's .xml)... if so, my questions are >"what" >>and "where". >> >>-----Original Message----- >>From: ext Shapira, Yoav [mailto:[EMAIL PROTECTED] >>Sent: Wednesday, January 14, 2004 11:47 AM >>To: Tomcat Users List >>Subject: RE: Manager - STOP application fails to stop session!!! >> >> >> >>Howdy, >>The default behavior is to persist sessions. You have to disable >>session persistence. Or if you really want them killed, write a class >>that implements both ServletContextListener and HttpSessionListener. >>Keep track of the sessions in a collection, adding when a session is >>created and removing when a session is destroyed. Then in the >>contextDestroyed event you can iterate through the remaining sessions >>and invalidate them all. This is not a perfectly clean approach, but >it >>might do the trick. >> >>Yoav Shapira >>Millennium ChemInformatics >> >> >>>-----Original Message----- >>>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >>>Sent: Wednesday, January 14, 2004 12:37 PM >>>To: [EMAIL PROTECTED] >>>Subject: Manager - STOP application fails to stop session!!! >>> >>>Stopping an application in Tomcat manager (either through browser or >>http >>>call) stops the app but does not terminate the associated sessions. >>> >>>How can you kill the sessions after stopping an application? >>> >>>Bruno Melloni >>>eBusiness Application Center, Americas >>>Nokia, Inc >>>6000 Connection Drive, Mailstop 4w223 >>>Irving, TX 75039 USA >>>*Office: +1 (972)894-6120 >>>*Cellular: +1 (469) 939-1067 >>>* SMS: [EMAIL PROTECTED] >>>* e-mail: [EMAIL PROTECTED] >>> >>> >>>--------------------------------------------------------------------- >>>To unsubscribe, e-mail: [EMAIL PROTECTED] >>>For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >>This e-mail, including any attachments, is a confidential business >>communication, and may contain information that is confidential, >>proprietary and/or privileged. This e-mail is intended only for the >>individual(s) to whom it is addressed, and may not be saved, copied, >>printed, disclosed or used by anyone else. If you are not the(an) >intended >>recipient, please immediately delete this e-mail from your computer >system >>and notify the sender. Thank you. >> >> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] >> >> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] > > > > >This e-mail, including any attachments, is a confidential business >communication, and may contain information that is confidential, >proprietary and/or privileged. This e-mail is intended only for the >individual(s) to whom it is addressed, and may not be saved, copied, >printed, disclosed or used by anyone else. If you are not the(an) intended >recipient, please immediately delete this e-mail from your computer system >and notify the sender. Thank you. > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
