logging-log4net-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Walden H. Leverich" <Wald...@TechSoftInc.com>
Subject RE: log4net and IIS problems
Date Wed, 27 Feb 2008 15:30:03 GMT
Since they _can_ be in a common process I guess w/cross-app-domain code
you could do something. But it's more likely that they're in different
processes anyway. Now you could do something w/some sort of
inter-process communication mechanism (MailSlot, Socket, shared memory,
etc.) but I don't know if I would. By the time you get there you might
as well just use something like a tcp appender to a remote process that
logs the rows into the logfile.




Walden H Leverich III
Tech Software
(516) 627-3800 x3051


Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)

From: Ron Grabowski [mailto:rongrabowski@yahoo.com] 
Sent: Wednesday, February 27, 2008 2:53 AM
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

----- 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