[jira] [Closed] (LOG4NET-645) Issue involving RollingFileAppender internal error

["Davyd McColl (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4NET-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davyd McColl closed LOG4NET-645.
--------------------------------
    Resolution: Fixed

As part of a renewed effort to get back on top of log4net issues, I'm closing out stale issues (2020 and later). If this issue persists, please re-raise it.

> Issue involving RollingFileAppender internal error
> --------------------------------------------------
>
>                 Key: LOG4NET-645
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-645
>             Project: Log4net
>          Issue Type: Bug
>    Affects Versions: 2.0.8
>         Environment: Windows 10
>            Reporter: Mario Puglisi
>            Priority: Major
>         Attachments: image-2020-02-20-09-36-51-602.png, image-2020-02-20-09-38-02-734.png
>
>
> We're getting random errors when using Log4net to log our kafka implementation messages, the errors are shown directly at console level, showing a message as the following:
> {code:java}
> log4net:ERROR RollingFileAppender: INTERNAL ERROR. Append is False but OutputFile [Destination of log.txt] already exists
> {code}
> The thing is that all our loggers are retrieved using an static implementation, where the "AppendToFile" option is true, it is also strange that the error happens after the logger had rolled over 3 or 4 backup files.
> It also appears to be somewhat writing to the file, even after the mentioned error occurs, because I have conducted tests deleting the log file mentioned in the error and it recreates the file and slowly fills it with the log data. Our concern is that some relevant data might be missing from the logs whenever the errors show up.
> Our C# logger implementation: 
>  !image-2020-02-20-09-36-51-602.png!
> All messages are logged using the "Info" level of the logger:
>  !image-2020-02-20-09-38-02-734.png!
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)