Sorry, seems I accidentially duplicated your answer. Btw: Why not just use the rolling file appender? -Erich
________________________________ From: Walden H. Leverich [mailto:[EMAIL PROTECTED] Sent: Wed 2008-02-27 16:30 To: Log4NET User Subject: RE: log4net and IIS problems X-ExchangeSecure-AntiSpam: valid(71) 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 -- Walden H Leverich III Tech Software (516) 627-3800 x3051 [EMAIL PROTECTED] http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.) From: Ron Grabowski [mailto:[EMAIL PROTECTED] 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 other... ----- Original Message ---- From: Morten Andersen <[EMAIL PROTECTED]> To: Log4NET User <[email protected]> Sent: Tuesday, February 26, 2008 8:14:10 AM Subject: log4net and IIS problems 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
