Return-Path: X-Original-To: apmail-logging-log4net-dev-archive@www.apache.org Delivered-To: apmail-logging-log4net-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F1E8479E7 for ; Fri, 14 Oct 2011 14:58:35 +0000 (UTC) Received: (qmail 47191 invoked by uid 500); 14 Oct 2011 14:58:35 -0000 Delivered-To: apmail-logging-log4net-dev-archive@logging.apache.org Received: (qmail 47123 invoked by uid 500); 14 Oct 2011 14:58:35 -0000 Mailing-List: contact log4net-dev-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Log4NET Dev" List-Id: Delivered-To: mailing list log4net-dev@logging.apache.org Received: (qmail 47102 invoked by uid 99); 14 Oct 2011 14:58:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Oct 2011 14:58:35 +0000 X-ASF-Spam-Status: No, hits=-1998.8 required=5.0 tests=ALL_TRUSTED,DEAR_SOMETHING,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Oct 2011 14:58:33 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 0ED353087BA for ; Fri, 14 Oct 2011 14:58:12 +0000 (UTC) Date: Fri, 14 Oct 2011 14:58:12 +0000 (UTC) From: "Stefan Bodewig (Commented) (JIRA)" To: log4net-dev@logging.apache.org Message-ID: <1344282020.14270.1318604292061.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (LOG4NET-178) Log4Net stops logging after appdomain recycle of aps.net2.0 application MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/LOG4NET-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127600#comment-13127600 ] Stefan Bodewig commented on LOG4NET-178: ---------------------------------------- @Matthiew: ConfigureAndWatch in your application start event was what I was thinking about, and using the full path won't hurt. @Ilpo: this is strange as it indicates the re-configuration inside the application start event didn't work. I assume turning on internal debugging of log4net still doesn't provide anything useful. > 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira