[LOG4NET-178] Log4Net stops logging after appdomain recycle of ASP.NET2.0 application

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 1.2.10
• Fix Version/s: 1.2.12
• Component/s: Appenders
• Environment: Windows server 2003
• Assignee: Dominik Psenner
• Reporter: Richard Nijkamp
• Created: 06/Oct/08 08:36
• Updated: 22/Jun/15 14:09
• Resolved: 29/Nov/12 08:12

Description

Dear sir/madam,

We are using Log4Net 1.2.10. We encounter the problem that Log4net doesn't continue logging after an event that triggers an appdomain recycle/restart.

In the global.asax we start the logging with:

private static readonly ILog log = LogManager.GetLogger(MethodBase.GetCurrentMethod().DeclaringType);

Logging works flawless when the application is started for the first time. After sometime it might occur that the appdomain gets recycled due to inactivity of the web application. We use the following code in Application_end():

log.Info("*** Application end ***");

log4net.LogManager.Shutdown();

After this function the application gets restarted and the Application_start() method executes and writes new lines to the log. The problem is that the log4net doesn't write the new lines after the restart. Could you explain why log4net might stop working after an appdomain restart of an asp.net2.0 web application? If I want log4net to work properly again I need to restart IIS manually.

Looking forward to your reply.

Best regards,

Richard Nijkamp

Issue Links

• is duplicated by: LOG4NET-200 Log4Net Dll stops logging after 1 or 2 days