Sessions aren't destroyed until the session times out. If you shut the server down, existing sessions will be written to file. If you bring the server back up before the timeout of those sessions, they will still exist upon server restart. If you think about it, this is usually desired behavior. I believe you can turn this off on the Coyote connector, but I've forgotten how. I can't imagine why you wouldn't want it to work this way. What if you were doing emergency server maintainance and had to restart the app while some users were connected. Blowing away their sessions would normally be undesired. You can always delete the work directory for the app if you actually do desire to blow away sessions as well.
Jake Quoting Joao Batistella <[EMAIL PROTECTED]>: > Hello! > > I'm using Tomcat 4 and all sessions that I have when the server is up are > not > destroyed when I shutdown te server. I've implemented a > ServletContextListener > to register when the app is going down and a HttpSessionListener to see when > a session is destroyed. When the server goes down the sessions are not > destroyed and, when it comes up again, the sessions are still there. If I > try to get a session attribute by some key before setting the same attribute > I have a result different of null. > Anyone knows what is this? > > My sofwate versions: > Windows XP Professional > Tomcat 4.1.29-LE > J2sdk 1.4.2 > > Thanks, > JP --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
