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, 07 Oct 2010 21:30:51 GMT
Hash: SHA1


On 10/6/2010 3:39 PM, Jane Muse wrote:
> There's a backgroundProcessor method in tomcat that checks whether
> container classes need to be reloaded, and checks for session
> expirations. Is it possible to disable this method, like you can disable
> class reloading for the context with reloadable="false"? I'm using
> tomcat 6.0.18 on an IBM i (OS400)  version V6R1. When daylight savings
> time hits, our application gets reloaded, and the following statements
> are in catalina.out: 
> Mar 14, 2010 3:00:08 AM org.apache.catalina.core.StandardContext reload
> INFO: Reloading this Context has started

Does this happen with every DST change that results in the clock being
set backward? I haven't looked at the code, but I can't imagine that the
BackgroundProcessor keeps the timestamp of the last file scan around for
comparison. Instead, I would expect logic similar to this:

while(true) {

  find files modified since last context startup

  if file list is non-empty, reload context

If the above logic is the actual implementation, then the only time
you'd have a problem is when you've deployed a webapp during the window
covered by the DST-clock-setback. For instance, if the clock goes from
02:00 early Sunday morning to 00:00 early Sunday morning, then you
should only experience some kind of confusion if you deploy between
00:00 and 02:00 the first time through early on Sunday morning.

I've never observed a DST clock-setback trigger a webapp reload.

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


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

View raw message