[ https://issues.apache.org/jira/browse/LOG4NET-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14660711#comment-14660711 ]
Maxim Cherednik commented on LOG4NET-469: ----------------------------------------- [~johnzabroski] .net 4.5, optimization enabled. I really wonder if this is by design... > Fixes for the LogicalThreadContext - NDC stack is wrong > ------------------------------------------------------- > > Key: LOG4NET-469 > URL: https://issues.apache.org/jira/browse/LOG4NET-469 > Project: Log4net > Issue Type: Bug > Components: Core > Affects Versions: 1.3.0 > Reporter: Maxim Cherednik > Fix For: 1.3.0 > > > This is related to issue number 455. (Link to github: > https://github.com/apache/log4net/pull/12) > I was playing around with this fix recently and came across some strange > behavior. > Imagine main method: > {code:title=main.cs|borderStyle=solid} > using (LogicalThreadContext.Stacks["NDC"].Push("Start")) > { > // init all the stuff here > _timer.TimerElapsed += TimerOnTimerElapsed; > } > {code} > An that would be it. > When I am on the timer tick event I have another context: > {code:title=timer.cs|borderStyle=solid} > using (LogicalThreadContext.Stacks["NDC"].Push("timer")) > { > Logger.Info("I am doing something here. Show me the context"); > } > {code} > As a result expect to see the context of the timer like this: "timer", > instead, I see: "Start timer" > Is this correct behavior? -- This message was sent by Atlassian JIRA (v6.3.4#6332)