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 41B111005F for ; Tue, 13 Jan 2015 12:54:33 +0000 (UTC) Received: (qmail 73918 invoked by uid 500); 13 Jan 2015 12:54:34 -0000 Delivered-To: apmail-logging-log4net-dev-archive@logging.apache.org Received: (qmail 73872 invoked by uid 500); 13 Jan 2015 12:54:34 -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 73862 invoked by uid 99); 13 Jan 2015 12:54:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Jan 2015 12:54:34 +0000 Date: Tue, 13 Jan 2015 12:54:34 +0000 (UTC) From: "Rick Weyrauch (JIRA)" To: log4net-dev@logging.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (LOG4NET-118) RollingFileAppender: RollingStyle=Size with StaticLogFileName=false does not work MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/LOG4NET-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275160#comment-14275160 ] Rick Weyrauch commented on LOG4NET-118: --------------------------------------- That is a fair question, but since I do not get any other messages regarding how or why the rename failed, it is difficult to say. I did look for a path where the rename could fail silently but did not see any, so I am a bit confused as to how it gets caused. No matter that problem, it cannot do anything that results in missing logs right - that is the primary concern here. So maybe it has to do something other than what is configured and either pick a different name, or, possibly better, append to the existing file even though APPEND is false. After some thought, I would vote to just append anyway even though that is not what was asked for. It will just try and do it all over again naturally wont it? So, raise the error each time and just keep appending. If the file gets too big and the logging application does not notice and react, it still ends badly, but at least they had a chance to go address their problem. And really, chances are, if it was a temporary condition, the file will rename correctly after a few attempts. The one problem will be that all the other files have already had their names bumped, so you only have to do the XXXXX top XXXXX.1 rename on the retries. Hope that is clear enough for a conversation starter. > RollingFileAppender: RollingStyle=Size with StaticLogFileName=false does not work > --------------------------------------------------------------------------------- > > Key: LOG4NET-118 > URL: https://issues.apache.org/jira/browse/LOG4NET-118 > Project: Log4net > Issue Type: Bug > Components: Appenders > Affects Versions: 1.2.10 > Environment: Windows 2003 / Microsoft .NET Framework 2.0 > Reporter: Patrick Gautschi > Priority: Minor > Fix For: 1.2 Maintenance Release > > > When using the an appender configuration like > > > > > > > > > > > > > > results in the following error message when the application is started the second time: > log4net:ERROR RollingFileAppender: INTERNAL ERROR. Append is False but OutputFile [V:\...\bin\Debug\info.log.0] already exists. -- This message was sent by Atlassian JIRA (v6.3.4#6332)