logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Katy Podolner <Katy.Podol...@aternity.com>
Subject RE: log timestamp not in sync with system time
Date Mon, 12 May 2008 07:37:32 GMT
Oh, I'm sorry, I was referring to my explanation and not at all to yours... Sorry for the misunderstanding

--Katy

-----Original Message-----
From: kadaba [mailto:sumanth_k@thbs.com]
Sent: Monday, May 12, 2008 7:44 AM
To: log4j-user@logging.apache.org
Subject: Re: log timestamp not in sync with system time


Well thanks for the explanation..
Sorry for the unsatisfactory explanation. I will Attach Images and hope it
will be clear to you.
The application is being launched in EDT timezone.
I will see if the update works.
http://www.nabble.com/file/p17181434/log.jpg


carnold-3 wrote:
>
>
> On May 11, 2008, at 2:00 AM, Katy Podolner wrote:
>
>> I'm afraid the information is entirely unsatisfactory, but I'll try
>> anyway.
>> If I recall correctly the situation in our case was as following :
>> System time -aka machine time -was 11:20 but the log time was 12:20
>> although it was a week or so before the date of the switch to
>> DST(when the machine time would be 12:20) . So it was as though Java
>> has already made the switch internally. After a week system time &
>> log time were the same without any changes on our part.
>>
>
> Sounds like you may have missed an update of the time zone data for
> your JVM.  The start of daylight savings time was moved up an week
> this year and if you had not updated your JVM, you'd see the behavior
> you described.  See http://java.sun.com/javase/tzupdater_README.html.
>
>
>> Does the 4 hours difference make any sense in terms of your
>> application or your timezone? Might it be the difference between
>> your time zone and GMT, for instance?  This might help you
>> understand the root of the problem.
>>
>> --Katy
>>
>
> The pattern layout is going to use default timezone.  If you are using
> different machines or are changing the default timezone, you may get
> unexpected results. If the default timezone is changing, I'd recommend
> that you use the EnhancedPatternLayout in the extras companion
> (http://logging.apache.org/log4j/companions/extras
> ) and specify an explicit timezone in the second set of braces,
> something like: "%d{}{GMT}"
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
>

--
View this message in context: http://www.nabble.com/log-timestamp-not-in-sync-with-system-time-tp17141276p17181434.html
Sent from the Log4j - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org


Mime
View raw message