[
https://issues.apache.org/jira/browse/LOG4NET-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625533#action_12625533
]
Ron Grabowski commented on LOG4NET-171:
---------------------------------------
The problem is that you have two different procesess trying to write/roll the
same file. If there are 3 processes writing/rolling the same file how does
log4net know when one of the other processes has rolled the file? Log4net can
easily handle lots of threads from the same process writing to a rolling file.
The message you're seeing shouldn't be crashing your application. Log4net
writes debug information to Console.Out when something bad happens. Your
program should continue to function...but logging will be disabled.
The next version of log4net has an improved configuration system that makes it
easier to detect configuration errors. Until then you can turn on internal
debugging and capture output sent to a System.Diagnostics listener.
If the jobs do overlap is it ok to have mixed output in the same file? Can you
log to a database then log to a file if the database goes offline?
> 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.
