Is this unique to hosting in Azure? Because we are using IIS 7.5 and
log4net works fine across restarts of our ASP.NET 4.x apps.

On Thu, Oct 25, 2012 at 1:34 AM, Phil Yardley (JIRA) <[email protected]>wrote:

>
>     [
> https://issues.apache.org/jira/browse/LOG4NET-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483975#comment-13483975]
>
> Phil Yardley commented on LOG4NET-178:
> --------------------------------------
>
> We've just come across this issue when hosting in Azure (IIS7.5) - logging
> stops on all our instances until we "kick" the application by changing the
> web.config.
>
> A bit concerned that this bug > 12 months old and makes the module useless
> on a daily basis.
>
>
>
> > 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
>

Reply via email to