tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filip Hanik - Dev Lists <devli...@hanik.com>
Subject Re: StandardManager behaviour when webapp stopped
Date Sat, 25 Nov 2006 23:45:11 GMT
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

Filip

Remy Maucherat wrote:
> 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 behaviour in these
>> circumstances is undefined. Is there a good reason not to invalidate
>> the active sessions in this case?
>>
>> Thoughts?
>
> I think it would be ok.
>
> Rémy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message