logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Barry (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LOG4NET-437) LogicalThreadContext data does not flow properly using Async and Await
Date Wed, 20 Aug 2014 13:42:28 GMT

     [ https://issues.apache.org/jira/browse/LOG4NET-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mike Barry updated LOG4NET-437:
-------------------------------

    Attachment: ThreadContextStacks.diff

Part 1 of a naive patch to solve the issue.

> LogicalThreadContext data does not flow properly using Async and Await
> ----------------------------------------------------------------------
>
>                 Key: LOG4NET-437
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-437
>             Project: Log4net
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.9, 1.2.10, 1.2.11, 1.2.12, 1.2.13
>         Environment: Windows 7, .NET 4.5
>            Reporter: Mike Barry
>         Attachments: LogicalThreadContext.diff, Program.cs, ThreadContextStacks.diff
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message