Mailing-List: contact log4net-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4NET User" <log4net-user@logging.apache.org>
Received-SPF: pass (nike.apache.org: domain of andrewarnott@gmail.com
 designates 209.85.216.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <878vmztsta.fsf@v35516.1blu.de>
References: 
 <CAE358b5erXeRXF7m+UhwxP06HPu22zZnAXGA1ZYWL9B45nRwtA@mail.gmail.com>
 <CAE358b5k5OUjWCOfnWCz2MevMs5LEHpkkiL83773=fsH7miJew@mail.gmail.com>
 <871ussb367.fsf@v35516.1blu.de>
 <CAE358b6h5h3htVho0c+AsJ0_=pGGk5tSGV1fdp-XFSWYqCYbEg@mail.gmail.com>
 <878vmztsta.fsf@v35516.1blu.de>
From: Andrew Arnott <andrewarnott@gmail.com>
Date: Tue, 29 Nov 2011 08:10:48 -0800
Message-ID: 
 <CAE358b7zSS-B=+MMvSRniMtF_2=ZeSyApb=AQUvhNk499wBAYQ@mail.gmail.com>
Subject: Re: ThreadLogicalContext not actually following logical threads
To: Log4NET User <log4net-user@logging.apache.org>
Content-Type: multipart/alternative; boundary=20cf3033465509ff8704b2e1de8e

--20cf3033465509ff8704b2e1de8e
Content-Type: text/plain; charset=ISO-8859-1

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.

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.

--
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 Mon, Nov 28, 2011 at 9:13 PM, Stefan Bodewig <bodewig@apache.org> wrote:

> On 2011-11-28, Andrew Arnott wrote:
>
> > The documentation is poor, I agree.  I had to stumble around quite a bit
> > before I figured out how to use it properly myself.  I believe the
> > difference may be that CallContext.*Logical*SetData requires the value to
> > be serializable, so that it can be cloned and applied to other threads,
> > perhaps even in separate appdomains.
>
> > This sounds like an area that log4net can improve then.
>
> For .NET 2+, yes.
>
> > I'm not sure why log4net claims to follow the logical thread when
> > apparently it doesn't.
>
> It probably does in some circumstances but obviously not all of them.
>
> > The good news is that in the absence of built-in support from log4net,
> I've
> > engineered a solution of my own by controlling the
> > HostExecutionContextManager in my AppDomain.  Whenever the logical thread
> > forks (i.e. threadpool use, c# 5 async keyword, etc.) my code "captures"
> > the current context stack from log4net and applies that stack to the new
> > thread, and "reverts" that change when the target thread has completed
> its
> > work for that call.
>
> > Pretty cool stuff, but it would be cooler if log4net had it built-in.
>
> Oh, feel free to help log4net improve here 8-)
>
> Cheers
>
>        Stefan
>

--20cf3033465509ff8704b2e1de8e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I&#39;d be happy to help. =A0But given the fact that I&#39;m a Microsoft em=
ployee with some strict open source restrictions, I can only provide suppor=
t for it. =A0<div><br></div><div>In short, if log4net stores its logical ca=
ll-tracking context stack using=A0<span class=3D"Apple-style-span" style=3D=
"color: rgb(34, 34, 34); font-family: arial, sans-serif; font-size: 13px; b=
ackground-color: rgba(255, 255, 255, 0.917969); ">CallContext.LogicalSetDat=
a and retrieves it using the similarly named method, everything should auto=
matically work. =A0If not, I can hopefully provide additional help.</span><=
/div>

<div><font class=3D"Apple-style-span" color=3D"#222222" face=3D"arial, sans=
-serif"><br clear=3D"all"></font>--<br>Andrew Arnott<br>&quot;I [may] not a=
gree with what you have to say, but I&#39;ll defend to the death your right=
 to say it.&quot; - S. G. Tallentyre<br>


<br><br><div class=3D"gmail_quote">On Mon, Nov 28, 2011 at 9:13 PM, Stefan =
Bodewig <span dir=3D"ltr">&lt;<a href=3D"mailto:bodewig@apache.org">bodewig=
@apache.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div class=3D"im">On 2011-11-28, Andrew Arnott wrote:<br>
<br>
&gt; The documentation is poor, I agree. =A0I had to stumble around quite a=
 bit<br>
&gt; before I figured out how to use it properly myself. =A0I believe the<b=
r>
</div>&gt; difference may be that CallContext.*Logical*SetData requires the=
 value to<br>
<div class=3D"im">&gt; be serializable, so that it can be cloned and applie=
d to other threads,<br>
&gt; perhaps even in separate appdomains.<br>
<br>
&gt; This sounds like an area that log4net can improve then.<br>
<br>
</div>For .NET 2+, yes.<br>
<div class=3D"im"><br>
&gt; I&#39;m not sure why log4net claims to follow the logical thread when<=
br>
&gt; apparently it doesn&#39;t.<br>
<br>
</div>It probably does in some circumstances but obviously not all of them.=
<br>
<div class=3D"im"><br>
&gt; The good news is that in the absence of built-in support from log4net,=
 I&#39;ve<br>
&gt; engineered a solution of my own by controlling the<br>
&gt; HostExecutionContextManager in my AppDomain. =A0Whenever the logical t=
hread<br>
&gt; forks (i.e. threadpool use, c# 5 async keyword, etc.) my code &quot;ca=
ptures&quot;<br>
&gt; the current context stack from log4net and applies that stack to the n=
ew<br>
&gt; thread, and &quot;reverts&quot; that change when the target thread has=
 completed its<br>
&gt; work for that call.<br>
<br>
&gt; Pretty cool stuff, but it would be cooler if log4net had it built-in.<=
br>
<br>
</div>Oh, feel free to help log4net improve here 8-)<br>
<br>
Cheers<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
 =A0 =A0 =A0 =A0Stefan<br>
</font></span></blockquote></div><br></div>

--20cf3033465509ff8704b2e1de8e--