[
https://issues.apache.org/jira/browse/LOG4NET-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14581858#comment-14581858
]
Dominik Psenner edited comment on LOG4NET-178 at 6/11/15 12:42 PM:
-------------------------------------------------------------------
Sorry Kamran, the consensus was that this issue can be fixed only by disabling
the overlapping rotation in the IIS configuration and it is the only fix
available. However, contributions are always welcome and if you find a better
way I want to encourage you to contribute your ideas!
For future readers, the issue arises by IIS that allows overlapping rotates.
The web application is then restarted without unloading log4net, but log4net
receives a "start" event while it is still running and right after that a
"stop" event which it handles by shutting down. Since the "start" event was
already sent it will be generated only with the next restart or reload and in
the meantime no logging happens at all. Configuring IIS to
DisallowOverlappingRotation=true makes sure that the "start" and "stop" events
arrive in order.
was (Author: nachbarslumpi):
Sorry Kamran, the consensus was that this issue can be fixed only by disabling
the overlapping rotation in the IIS configuration and it is the only fix
available. However, contributions are always welcome and if you find a better
way I want to encourage you to contribute your ideas!
For future readers, the issue arises by IIS that allows overlapping rotates.
The web application is then restarted without unloading log4net, but log4net
receives a "start" event while it is still running and right after that a
"stop" event which it handles by shutting down. Since the "start" event was
already sent it will be generated only with the next restart or reload and in
the meantime no logging happens at all.
> 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)
