logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kamran (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (LOG4NET-178) Log4Net stops logging after appdomain recycle of ASP.NET2.0 application
Date Tue, 16 Jun 2015 05:44:00 GMT

    [ https://issues.apache.org/jira/browse/LOG4NET-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587501#comment-14587501
] 

Kamran edited comment on LOG4NET-178 at 6/16/15 5:43 AM:
---------------------------------------------------------

There is no doubt problem is during App domain recycle. 
One error I found from log4net debug log is about my adonet appender setting is 

ERROR XmlHierarchyConfigurator: Cannot find Property [immediateFlush] to set object on [log4net.Appender.AdoNetAppender]

My adonet appender settings look like

 <appender name="AdoNetAppender" type="log4net.Appender.AdoNetAppender">
   <immediateFlush value="true" />
    <bufferSize value="0" />
....

So now i am commenting out immediateFlush property (which might have been copied from RollingFileAppender
Settings) and will see if the problem still exists or not


was (Author: kamii47):
There is no doubt problem is during App domain recycle. 
One error I found from log4net debug log is about my adonet appender setting is 

ERROR XmlHierarchyConfigurator: Cannot find Property [immediateFlush] to set object on [log4net.Appender.AdoNetAppender]

My adonet appender settings look like

 <appender name="AdoNetAppender" type="log4net.Appender.AdoNetAppender">
   <immediateFlush value="true" />
    <bufferSize value="0" />
....

So now i am commenting out immediateFlush property and will see if the problem still exists
or not

> 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)

Mime
View raw message