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 Wed, 13 Oct 2010 18:25:51 GMT
Hash: SHA1


On 10/13/2010 1:51 PM, Jane Muse wrote:
> I found that reloadable="false" does not suppress tomcat from watching
> if files change in WEB-INF/lib, even though the docs say it does: 

Please log a bug. Note that bugs logged against old versions of Tomcat
(6.0.18 is over two years old) are often met with "upgrade to latest,
then retest" instructions.

Upgrading would certainly be a good idea in general.

> Can I safely say I've run into both an IBM and a tomcat bug?

I'm not convinced that either are true, honestly. There are plenty of
explanations that do not require either your OS or Tomcat to have a bug.

> I'm on
> tomcat 6.0.18 and I've searched the 6.0.29 change logs, didn't see
> anything for this issue that's been fixed.

We run in production on 5.5.x and 6.0.x both with default "reloadable"
values (that is, "false") and changes to files in WEB-INF/classes and
WEB-INF/lib do not trigger automatic reloads. My experience leads me to
believe that Tomcat works properly and that your configuration is
somehow broken.

Can you post your TOMCAT_HOME/conf/context.xml file as well as your
webapp's META-INF/context.xml file? Take care to remove sensitive
information, particularly from the latter.

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


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

View raw message