tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <wbar...@wilshire.com>
Subject Re: Question about Session in Tomcat 3.3 -- continued...
Date Mon, 12 Aug 2002 19:42:47 GMT
Yes, it seems to be true that sessions are lost on reloading with
fullReload=true.  I don't think that the case of fullReload=false has been
tested much, so it is possible that there could be some strange bugs like in
3.2.x.

It looks like the best way to fix this (for the default fullReload=true
case) would be to add another hook to the API (e.g. copyContext(Context old,
Context new)).  This way, SimpleSessionStore could move the old sessions
into the new Context before they get destroyed.

Comments?

----- Original Message -----
From: "Hugh J. L." <hughjlee@yahoo.com>
To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Sent: Monday, August 12, 2002 5:50 AM
Subject: Question about Session in Tomcat 3.3 -- continued...


> I changed switch "fullReload" in ReloadInterceptor
> from true to false, and sessions are maintained
> through context reloading. (Of course, because the old
> context remains.) Is there any disadvantage if I set
> this way? Anyway fullReload=true is default setting.
>
> Thanks.
>
> Hugh
>
>
> __________________________________________________
> Do You Yahoo!?
> HotJobs - Search Thousands of New Jobs
> http://www.hotjobs.com
>
> --
> To unsubscribe, e-mail:
<mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
<mailto:tomcat-dev-help@jakarta.apache.org>
>


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


Mime
View raw message