tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filip Hanik - Dev Lists <>
Subject Re: StandardManager behaviour when webapp stopped
Date Sun, 26 Nov 2006 00:58:34 GMT
You can still cluster just using AOP without ever involving the manager, 
hence such solutions would be affected by this new behavior.
at most, when a webapp is shutdown, you can call passivate, but not 
invalidate the sessions.

Remy Maucherat wrote:
> Filip Hanik - Dev Lists wrote:
>> 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 if we 
>> mean to change it
> The clustered manager most likely would have the opportunity to 
> override the code which would do the expiration, I think.
> Rémy
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message