Details
Description
LogicalThreadContext doesn't work properly when using Async and Await. The current NDC call stack gets corrupted because the logical data context is not immutable. (See: http://blog.stephencleary.com/2013/04/implicit-async-context-asynclocal.html for the gory details). I've attached a Program.cs that demonstrates the issue. You will see with an unpatched log4net the thread context is corrupted compared to the proper implementation in MyStack and the console logger. An entry like:
LOG4NET Main 1 A 2 A: </MoreWork>
LOG4NET Main 1 A 2 A: </MoreWork>
is invalid and should not be possible in a properly working thread context.
I've attached a VERY naive patch that corrects the issue.
Attachments
Attachments
Issue Links
- duplicates
-
LOG4NET-455 LogicalThreadContext does not flow correctly through async/await
- Resolved