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 Fri, 08 Oct 2010 14:24:13 GMT
Hash: SHA1


On 10/8/2010 4:44 AM, Mark Thomas wrote:
> On 08/10/2010 01:11, Jane Muse wrote:
>> This happens with both DST and standard time changes. What's interesting
>> is if we go back in time to Oct 29 2006, it does not occur. From March
>> 2007 forward, every fall and spring we get the error when the
>> application reloads. The DST time change rules changed in March 2007 for
>> USA time zone.
> Random thought. Have the necessary timezone updates been applied to the
> OS and to Java? If they are out of sync that could make time appear to
> jump to the JVM.

+1 on the hunch, thought I'm still not sure why Tomcat would perform a
knee-jerk reload unless the initial deployment occurred during the
indeterminate interval between the clock adjustment end points (boy,
this is awkward to discuss).

We had a problem a few years ago in production where Java hadn't been
updated with the new DST rules but the OS had. We try to use NOW() in
our database queries as much as possible, but sometimes it makes much
more sense to just generate a new java.util.Date object for timestamps
and then use those in our SQL queries as well. Due to that incident, we
ended up with records in our database that appeared to have been updated
before they had been created. Oops.

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


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

View raw message