Logging Application Block (flat file) creates 2 simultaneous log files

Topics: Logging Application Block
Jul 16, 2008 at 2:10 PM
I'm using Logging Application Block (3.1) rolling flat file trace listener to debug an ASP.NET 2 web app (aspx).

After a debugging session, two separate log files are created.
One is called:
 ...(as expected), the other is called:

Why is this?
(I'm thinking "Web Farm" or somehow two separate application domains for the same app.)
Say the client: "We do not use a web farm", and I'm sure they have only one webserver.

The two files contain interspersed entries for overlapping time from the same user/session ID/clientIP.

Next will be to add logging for the server IP and AppDomainName.
I am having problems with the Session state (thus the debugging).

Jul 16, 2008 at 2:47 PM
Could this: http://www.codeplex.com/entlib/Thread/View.aspx?ThreadId=25021 apply to you?
Jul 17, 2008 at 1:37 AM

SSG31415926 wrote:
Could this: http://www.codeplex.com/entlib/Thread/View.aspx?ThreadId=25021 apply to you?

I don't think it directly applies, because I'm not using EHAB (only using LAB), and the fix mentioned is to EHAB.
I'm not creating my own logwriter either (joshmshrf's case); I'm just calling Logger.Write(...).

It does explain the GUID on the front of the log file name however: seems that is what happens when the file is already opened/locked and another "something" tries to open it for writing.

Jul 17, 2008 at 6:46 AM
The answer was "IIS 6 Web Garden".
The app is now in an app pool with only one worker process and working well.