Remy/Filip,
Thanks for your input. I'll update the bug report with a brief summary
and come back to this later.
Mark
Filip Hanik - Dev Lists wrote:
You can still cluster just using AOP without ever involving the manager,
hence such solutions would be affected by this new behavior.
at most,
Mark Thomas wrote:
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
it will cause problems for clustered stuff, not sure that container
shutdown means session invalidation.
for example, if you invalidate the session, such a change would trickle
through the cluster, and that might not be intentional.
I suggest we leave the behavior as is, or at least configurable
