logging-log4net-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erich Eichinger" <E.Eichin...@diamonddogs.cc>
Subject RE: log4net and IIS problems
Date Wed, 27 Feb 2008 19:29:17 GMT
As AppDomains are completely isolated from each other, it needs some IPC mechanism for this.
A common solution on windows is to create a named Mutex or a named Event as named objects
are visible across multiple processes on a machine.


From: Ron Grabowski [mailto:rongrabowski@yahoo.com]
Sent: Wed 2008-02-27 08:53
To: Log4NET User
Subject: Re: log4net and IIS problems

I wonder if there's any way for the two AppDomains to be aware of each other...

----- Original Message ----
From: Morten Andersen <morten@vianett.no>
To: Log4NET User <log4net-user@logging.apache.org>
Sent: Tuesday, February 26, 2008 8:14:10 AM
Subject: log4net and IIS problems



I am using log4net on my asp.net web page hosted at an IIS server. This seems to work just
fine until I do some changes in the source. Since asp.net runs as a shadow copy, changes will
be compiled on the next request after the change was made. I guess this causes the log manager
to duplicate itself, and the second one will not have write access to the log files. Since
the old app domain will not die before all the requests are completed, the new log manager
must wait for this pool to die before enabling the appenders. An alternative solution can
be that the log manager retries to create the appenders if it fails.


Maybe it already exist a solution for this problem?


Best regards,

Morten Andersen

View raw message