tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <>
Subject StandardManager behaviour when webapp stopped
Date Sat, 25 Nov 2006 16:39:40 GMT
Bug 40593 [1] has raised the following question:

When a web app with valid sessions is stopped and the StandardManager
is configured not to serialize the sessions what, if anything, should
the container do in this case?

As far as I can tell from the spec, the container behaviour in these
circumstances is undefined. Is there a good reason not to invalidate
the active sessions in this case?




To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message