[
https://issues.apache.org/jira/browse/LOG4NET-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4NET-433:
--------------------------------
LOG4NET is now dormant.
> ThreadContext property not written to log when running on mono
> --------------------------------------------------------------
>
> Key: LOG4NET-433
> URL: https://issues.apache.org/jira/browse/LOG4NET-433
> Project: Log4net
> Issue Type: Bug
> Components: Appenders
> Environment: log4net 2.0.3 (Nuget version)
> .Net version 4.0
> Reporter: Dan Ingalla
> Priority: Major
>
> When running the assembly under Mono, a thread context property displays as
> 'null' in the log entries. This does not occur on when running on the MS CLR.
> I verified the property is getting set via direct console output.
> E.g.
> {code}
> ThreadContext.Properties["requestId"] = "_system_process";
> var id = ThreadContext.Properties["requestId"];
> Console.WriteLine("Request ID from thread context: {0}", id);
> // Outputs: Request ID from thread context: _system_process
> {code}
> Now on both MS .Net and Mono the console output verifies that the thread
> context value is being set, but only while running under the MS CLR does the
> request Id value get written to any logs. In Mono, the output is null.
> This sounds like a Mono issue, but I figured I would report it anyway.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
