Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 47803 invoked by uid 500); 31 Jul 2001 13:29:25 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: tomcat-dev@jakarta.apache.org Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 47637 invoked from network); 31 Jul 2001 13:29:24 -0000 Date: Tue, 31 Jul 2001 23:36:28 +1000 From: Dmitri Colebatch X-Sender: dim@dim.coxless.com To: tomcat-dev@jakarta.apache.org, "Rob S." Subject: Re: Log date formatting? In-Reply-To: <200107311252.f6VCqHe08621@rm-rstar.sfu.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N >From memory java.util.Calendar does a terrible job of paying attention to the underlying o/s settings. I live in Sydney, and courtesy of the Olympics last year we started daylight savings ridiculously early - changed all the o/s timezones, but the Calendar class refused to pick it up, so we had to set the default timezone manually ourselves.... I'm guessing this is the same thing On Tue, 31 Jul 2001, Rob S. wrote: > 2001-07-31 07:46:21 - Ctx( /WebConfigure ): JasperException: [snip] > > /tmp > date > Tue Jul 31 19:49:52 EDT 2001 > > Shouldn't the logs be in 24hr? > > ...and yes, the time is horribly out of sync on that machine =) > > - r > >