logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ron Grabowski (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (LOG4NET-156) Probable I/O race condition detected while copying memory.
Date Sat, 14 Jun 2008 14:19:45 GMT

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

Ron Grabowski resolved LOG4NET-156.

    Resolution: Invalid
      Assignee: Ron Grabowski

The RollingFileAppender/MinimalLock combination most likely won't work with 250+ users....RollingFileAppender/MinimalLock
isn't a database! If you must use a RollingFileAppender use a MutextLock instead.

> Probable I/O race condition detected while copying memory. 
> -----------------------------------------------------------
>                 Key: LOG4NET-156
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-156
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.2.10
>         Environment: Windows XP Professional
>            Reporter: siva
>            Assignee: Ron Grabowski
>             Fix For: 1.2.10
> Currently we are facing some issues with the log4net configuration in our project. I
am looking for help on this.
> We are getting the following error in the log4net log file:
> Error: Probable I/O race condition detected while copying memory. The I/O package is
not thread safe by default. In multithreaded applications, a stream must be accessed in a
thread-safe way, such as a thread-safe wrapper returned by TextReader's or TextWriter's Synchronized
methods. This also applies to classes like StreamWriter and StreamReader.] 
> We are using the rollinglogfileAppender with the rolling style as "Date" and the locking
model as "log4net.Appender.FileAppender+MinimalLock".
> When nearly 250 users in our application tries to write to the log file it is coming
with the above error message.
> Any help is greatly appreciated.

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

View raw message