You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Craig R. McClanahan" <cr...@apache.org> on 2001/12/04 23:59:06 UTC
Re: Application variables timeout under Tomcat
On Wed, 5 Dec 2001 julien-martin@wanadoo.fr wrote:
> Date: Wed, 5 Dec 2001 00:14:25 +0100
> From: julien-martin@wanadoo.fr
> Reply-To: Tomcat Users List <to...@jakarta.apache.org>
> To: Tomcat Users List <to...@jakarta.apache.org>
> Subject: Application variables timeout under Tomcat
>
> I am running Tomcat 4.0.1 and I would like to know how long application
> variables are kept in memory. Do they eventually timeout or are they kept
> in memory until the next server reboot?
> Can anyone help?
> Thanks in advance,
> Julien.
>
The answer depends on what you mean by "application variables". The only
time Tomcat *ever* removes anything is under the following circumstances:
* Your session times out --> all session attributes are
removed. They will be available for garbage collection
unless your application maintains other references to them.
* Your application is restarted (either because you have reloadable
set to true or you used the Manager app) --> all classes loaded
from /WEB-INF/classes and /WEB-INF/lib (and all instances of those
classes) are thrown away, and your web app is restarted with a new
class loader. Note that this does *not* affect classes loaded
from "common/lib" or "lib".
* Tomcat is shut down --> everything is removed.
Craig McClanahan
--
To unsubscribe: <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>