[
https://issues.apache.org/jira/browse/LOG4NET-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625355#action_12625355
]
Steven Myron commented on LOG4NET-171:
--------------------------------------
We are trying to work with the client and get the jobs spaced out so they don't
have the potential to overlap. This is for a SAP integration project that
syncs up data between two disparate systems.
I had been using log4j in a web app environment that had multiple sessions,
servlets, and threads logging to the same file in a high volume usage scenerio.
We never had any problems with the logging (our hands were full with other
issues). We also used a RollingFileAppender (on date/time rather than size).
The Apache website states that is logging is fail-stop and not reliable and if
logging is interrupted (database connection, network, "file sharing violation",
etc.) that the worst case is that it just doesn't log that event (no problem).
Right now, I am trying a "PatternFileAppender" to change folder/file locations
for different plants. I had to create a class from source code I found from a
reference on apache.org but not working so far...when log4net configures it is
hard to tell if it is configuring properly (which in this case it is not since
I am not seeing any appenders)?
Hey, I love this logger and it just caught me by surprise when I saw it crash
an application for the first time ever for me? This ain't supposed to happen...
> 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.
