[ https://issues.apache.org/jira/browse/LOG4NET-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14581753#comment-14581753 ]
Kamran edited comment on LOG4NET-178 at 6/11/15 10:15 AM: ---------------------------------------------------------- My question is why this is marked as resolved in 1.2.12 even if it is still exists in latest version (currently 1.2.13) version. I can't allowed to change DisallowOverlappingRotation on my production system. This has to be reopened and properly handled.I have logging in mysql db as well as in file. Same problem doesn't appear in RollingFileAppender. I have number of web services. And I don't want's to put log4net configure in each service constructor as it will be a performance impact. Any Idea about how can i manage it in Application_start event of glabal.asax.cs was (Author: kamii47): My question is why this is marked as resolved in 1.2.12 even if it is still exists in latest version (currently 1.2.13) version. I can't allowed to change DisallowOverlappingRotation on my production system. This has to be reopened and properly handled.I have logging in mysql db as well as in file. Same problem doesn't appear in RollingFileAppender. > Log4Net stops logging after appdomain recycle of ASP.NET2.0 application > ----------------------------------------------------------------------- > > Key: LOG4NET-178 > URL: https://issues.apache.org/jira/browse/LOG4NET-178 > Project: Log4net > Issue Type: Bug > Components: Appenders > Affects Versions: 1.2.10 > Environment: Windows server 2003 > Reporter: Richard Nijkamp > Assignee: Dominik Psenner > Fix For: 1.2.12 > > > 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)