[
https://issues.apache.org/jira/browse/LOG4NET-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504485#comment-13504485
]
Ilpo Juvander commented on LOG4NET-178:
---------------------------------------
Above configuration is not the whole truth. What we originally had was exactly
like it is for desktop application, using this [assembly:
log4net.Config.XmlConfigurator(ConfigFile = "log4net.config", Watch = true)].
It does not really matter what the file name is, logging just ends at some
point when IIS is recycling application pools.
There is some timing issue how this configuration/shutdown is handled.
Application start seems to happen before previous shutdown is called thus even
new instance gets logging shutdown. Using configuration call from class
constructor is *late* enough so that it really does the initialization for new
instance and does not get this shutdown call from previous application pool. We
have used this method now for years in hundreds of installations on different
environments and works 100% of the time.
Sometimes this happens, sometimes not. On some environments this happens
immediately, on some it takes a while to reappear, but it will eventually be
there.
> Log4Net stops logging after appdomain recycle of aps.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
> Fix For: 1.2 Maintenance Release
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
