You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4net-dev@logging.apache.org by "Steven Myron (JIRA)" <ji...@apache.org> on 2008/08/27 17:05:44 UTC

[jira] Closed: (LOG4NET-171) Log file locking causing an error to be thrown from the RollingFileAppender

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

Steven Myron closed LOG4NET-171.
--------------------------------

    Resolution: Invalid

Please see my last comment

> Log file locking causing an error to be thrown from the RollingFileAppender
> ---------------------------------------------------------------------------
>
>                 Key: LOG4NET-171
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-171
>             Project: Log4net
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.10
>         Environment: Windows 2003 Server (scheduled jobs/.exe that may be overlapping)
>            Reporter: Steven Myron
>            Priority: Critical
>         Attachments: original issue.jpg
>
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> Scheduled processes (~ 15 minutes apart) seem to be overlapping possibly causing file sharing violations for the log file that log4net is writing to.  This file is statically named and is written to using the RollingFileAppender.  This abruptly terminates the application and presents an unexpected error to the client.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.