tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: Disable class monitoring for reloading container classes
Date Thu, 14 Oct 2010 14:54:09 GMT
Hash: SHA1


On 10/13/2010 5:41 PM, Jane Muse wrote:
> We have a directory called COMPANY_NAME/tomcat that is CATALINA_BASE. 
> I sent the contents of CATALINA_BASE/conf/context.xml in the email
> below.

Great. It's probably not necessary to comment-out the <WatchedResource>
as the context should not be reloadable if you set reloadable="true",
though I haven't tried actually 'touch'ing web.xml just to see if it
would trigger a context reload.


Okay. If you have a standard server.xml, that means that APP_NAME will
be deployed to "/APP_NAME" automatically, unless you have <Host

> We also have a COMPANY_NAME/APP_CONF_DIR that contains a /conf
> directory, the APP_NAME.war file, and an APP_NAME.xml file.

Those files will be ignored unless there are other configuration
settings that make them relevant.

> There is a
> context element defined in the COMPANY_NAME/APP_CONF/DIR/app_name.xml
> file with reloadable="false". This is the one I was changing. However it
> turns out that we used this one as a placeholder in case the one in the
> CATALINA_BASE/conf/[enginename]/[hostname]/app_name.xml got deleted.

That sounds like a good plan. Again, the file you were editing was not
being consulted by Tomcat. You'll need to copy that file into

As Chuck states, you must remove the "path" attribute from the <Context>
element: it will be ignored at best and cause a double-deployment (or
failed deployment) at worst. Or, it might cause your webapp to reload
for unknown reasons :)

> We also have a context element in a place I hadn't seen before at:
> CATALINA_BASE/conf/[enginename]/[hostname]/app_name.xml. This context
> element had reloadable="true". I changed it to reloadable="false" and
> restarted tomcat. Now the app does not get reloaded! Fixed. Thanks to
> all.

This was going to be my final attempt: that you were editing the wrong
configuration file.

Still, we'd love to hear the resolution of the file timestamp changing
when DST kicks-in. Please let us know what you find out.

- -chris
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla -


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

View raw message