Steve Ziuchkovski created LOG4NET-380:
-----------------------------------------
Summary: 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
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
