logging-log4net-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ron Grabowski <rongrabow...@yahoo.com>
Subject Re: log4net and IIS problems
Date Wed, 27 Feb 2008 07:53:12 GMT
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

  
<!--
 _filtered {font-family:"Cambria Math";panose-1:2 4 5 3 5 4 6 3 2 4;}
 _filtered {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri", "sans-serif";}
a:link, span.MsoHyperlink
	{color:blue;text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;text-decoration:underline;}
span.EpostStil17
	{font-family:"Calibri", "sans-serif";color:windowtext;}
.MsoChpDefault
	{}
 _filtered {margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
	{}
-->
Hi
   
 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
 




Mime
View raw message