Without looking at your source code, no idea. I have just checked the Tomcat source and every attribute that implements HttpSessionActivationListener will have sessionWillPassivate() and sessionDidActivate() called.
At the moment it looks like something in your app. Mark > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Andreas Schildbach > Sent: Sunday, April 18, 2004 7:28 PM > To: [EMAIL PROTECTED] > Subject: Re: Detecting Sessions already existent at Tomcat Startup? > > Hello Mark, > > > <spec-quote> > > SRV.15.1.8 HttpSessionActivationListener > > </spec-quote> > > > > HttpSessionActivationListener is the way to achieve what > you are trying to do. > > Then why doesn't Tomcat 5.0.19 call my registered > HttpSessionActivationListener when I shut Tomcat down or > start it up again? > > I know that my sessions are being persisted, because > > a) I see the my sessions attributes appearing in SESSION.ser and > b) I can still access the session after restarting Tomcat if > I keep my > browser open. > > Regards, > > Andreas > > > > > --------------------------------------------------------------------- > 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]
