Thanks for fixing this, Stefan. I haven't looked at your checkin itself (r1207948 apparently), but just a heads up, that unless you're using an immutable stack, you may want to verify that the stack doesn't corrupt itself from threads with different contexts modifying the same object. I'm not sure whether the objects automatically get serialized or not--if not, then you probably need to use an immutable stack<http://blogs.msdn.com/b/ericlippert/archive/2007/12/04/immutability-in-c-part-two-a-simple-immutable-stack.aspx> . -- Andrew Arnott "I [may] not agree with what you have to say, but I'll defend to the death your right to say it." - S. G. Tallentyre
On Tue, Nov 29, 2011 at 8:22 AM, Stefan Bodewig <bode...@apache.org> wrote: > On 2011-11-29, Andrew Arnott wrote: > > > I'd be happy to help. But given the fact that I'm a Microsoft employee > > with some strict open source restrictions, I can only provide support for > > it. > > OK, understood. And thank you for your support. > > > In short, if log4net stores its logical call-tracking context stack > > using CallContext.LogicalSetData and retrieves it using the similarly > > named method, everything should automatically work. If not, I can > > hopefully provide additional help. > > https://issues.apache.org/jira/browse/LOG4NET-317 > > and should be fixed pretty soon. > > Thanks > > Stefan >
