Return-Path: X-Original-To: apmail-logging-log4net-dev-archive@www.apache.org Delivered-To: apmail-logging-log4net-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5961B100E2 for ; Fri, 31 May 2013 09:28:25 +0000 (UTC) Received: (qmail 42146 invoked by uid 500); 31 May 2013 09:28:25 -0000 Delivered-To: apmail-logging-log4net-dev-archive@logging.apache.org Received: (qmail 41965 invoked by uid 500); 31 May 2013 09:28:22 -0000 Mailing-List: contact log4net-dev-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Log4NET Dev" List-Id: Delivered-To: mailing list log4net-dev@logging.apache.org Received: (qmail 41903 invoked by uid 99); 31 May 2013 09:28:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 May 2013 09:28:20 +0000 Date: Fri, 31 May 2013 09:28:20 +0000 (UTC) From: "Dominik Psenner (JIRA)" To: log4net-dev@logging.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (LOG4NET-380) LoggingEvents received from RemoteAppender are UTC, but TimeStamp.Kind is "Local" and not "Utc" MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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