Thanks Michael. I noticed that this thread priority is set to highest, whereas other are not (usually). I guess this closes the topic :)
regards Thibaut On Wed, 6 Oct 2004 11:53:54 -0400, Stricklen, Michael W <[EMAIL PROTECTED]> wrote: > Internal threads (those created by the .NET runtime) definitely show up in > the VS.NET debugger. > > Regards, > Michael Stricklen > Sr. Software Engineer > Computer Associates > > > > -----Original Message----- > From: Thibaut Barr�re [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 06, 2004 11:37 AM > To: [EMAIL PROTECTED] > Cc: Log4NET User > Subject: Re: Does log4net start its own thread ? > > Hi Dag, thanks for your reply; > > I'm monitoring System.Threading.Thread threads through the debugger. > Running the sample I posted before in step by step debug shows that a > new thread is created on the first attempt to call GetLogger. > > As I don't start any thread in the sample, it's either some internal > .Net thread or a log4net created thread (in the sample I didn't > configure any kind of appenders, RemotingAppender other, in the config > file). > > I'm just starting to name threads so I don't know if internal .Net > threads are supposed to show up in the debugger. But if you confirm > that apart the RemotingAppender there's not use of threads in log4net, > I guess it must be something internal then... > > cheers > > Thibaut > >
