On 27.09.2010 15:42, jmorati...@dit.upm.es wrote:

Many thanks Caldarale. I'm working with tomcat 6, but a I was looking so
quickly for an answer that I didn't realise that it was the tomcat 3.2
user manual, but that explained me what happened.

I think that<WatchedResource>  will help me for this kind of tasks

Note that the watched resources means Tomcat will reload the webapp. I had the impression, you wanted to use a self-made mechanism that watches a resource and does some internal reconfiguration when the resource changes - but not a complete reload of the webapp.

Regards,

Rainer


From: jmorati...@dit.upm.es [mailto:jmorati...@dit.upm.es]
Subject: Re: About ContainerBackgroundProcessor thread


Here is the explanation I found:
http://tomcat.apache.org/tomcat-3.2-doc/uguide/tomcat_ug.html

You can't seriously be using Tomcat 3.2, are you?  That hasn't been
supported for eons.

In regards to your original question, if the reloadable attribute of the
<Context>  element is set to true, Tomcat will monitor /classes/ to see if
the webapp has been updated.  To quote from current documentation:

"Set to true if you want Catalina to monitor classes in /WEB-INF/classes/
and /WEB-INF/lib for changes, and automatically reload the web application
if a change is detected. This feature is very useful during application
development, but it requires significant runtime overhead and is not
recommended for use on deployed production applications."

You can also use a nested<WatchedResource>  element to trigger reloads for
other files; the default is just WEB-INF/web.xml.  If you don't set
reloadable and don't specify the file as a<WatchedResource>, Tomcat
should not attempt to do anything with the webapp once it's started.

But if you really are using Tomcat 3.2, I have no idea what it's behavior
should be; move up to a supported level.

  - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to