logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominik Psenner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4NET-380) LoggingEvents received from RemoteAppender are UTC, but TimeStamp.Kind is "Local" and not "Utc"
Date Fri, 31 May 2013 09:28:20 GMT

    [ https://issues.apache.org/jira/browse/LOG4NET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671282#comment-13671282
] 

Dominik Psenner commented on LOG4NET-380:
-----------------------------------------

As far as I know .NET does convert a DateTime to the computers local time when it is deserialized.
This is actually expected and I can't quite understand why log4net should try to work around
that? If you wanted all timestamps to be UTC, you could still invoke http://msdn.microsoft.com/en-us/library/system.datetime.touniversaltime(v=vs.100).aspx
on the machine that receives all logging events or even change the timezone of that machine
to be UTC.
                
> LoggingEvents received from RemoteAppender are UTC, but TimeStamp.Kind is "Local" and
not "Utc"
> -----------------------------------------------------------------------------------------------
>
>                 Key: LOG4NET-380
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-380
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.2.11
>         Environment: .NET 4 application on RaspberryPi (Arch Linux) with Mono 2.10.9,
logging with RemoteAppender to an application on Windows 7, which uses a custom appender to
add the received LoggingEvents to a collection.
>            Reporter: Steve Ziuchkovski
>              Labels: remote, timestamp, timezone
>
> The timestamps from RemoteAppender are UTC, but the TimeStamp.Kind property is "Local".
> Both the Windows and Linux machines have their system time set to local time.
> The LoggingEvent TimeStamps that are received from the Windows machine (not going through
RemoteAppender) contain local timestamps, and the LoggingEvent.TimeStamp.Kind is "Local".
> The LoggingEvent TimeSTamps that are received from the Linux machine (going through RemoteAppender)
contain UTC timestamps, but the TimeStamp.Kind is "Local", not "Utc".
> If the Kind property was UTC, I could adjust the timestamps from both log event sources
to match (both UTC/both Local). Unfortunately, I cannot tell the difference using just the
TimeStamp field itself.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message