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 "siva (JIRA)" <ji...@apache.org> on 2008/05/21 22:55:55 UTC
[jira] Commented: (LOG4NET-156) Probable I/O race condition
detected while copying memory.
[ https://issues.apache.org/jira/browse/LOG4NET-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598788#action_12598788 ]
siva commented on LOG4NET-156:
------------------------------
Any help on this will be greatly appreciated.
Thanks,
Siva
> 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
> 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.