In addition I received this reply from Nicko Cadell that may help too:

-----------
This is a known issue fixed in log4net 1.2.10. Please download the latest 
version from http://logging.apache.org/log4net/downloads.html

The exception is actually coming from an internal error handler. The Appender 
must have thrown an exception for this code path to be activated. The 
log4net.Util.LogLog.Error is used to log internal errors.

The log4net.Util.LogLog.Error writes to the console, and the 
System.Diagnostics.Trace handler. It looks like Console code isn't working 
correctly.


This is not recommended but If you must use log4net 1.2.9 then you can disable 
the internal error logging by setting the following <appSettings> in your 
application's .config file:

<appSettings>
  <add key="log4net.Internal.Quiet" value="true" /> </appSettings>

Cheers,
Nicko
----------- 


Regards
Ian Dykes
 
-
 
Software Developer
Esendex Ltd
49 Stoney Street
Nottingham NG1 1LX
 
http://www.esendex.com
 
Tel: +44 (0) 115 959 7962
Fax: +44 (0) 115 959 7966

Recommend Esendex's Business SMS service to a friend or colleague and you can 
earn up to £100 in High Street Gift Vouchers when they sign up. 

Go online to make your recommendation today. 
https://www.esendex.com/uk/recommend/recommend.aspx 
-----Original Message-----
From: Michelle Weber [mailto:[EMAIL PROTECTED] 
Sent: 05 September 2006 14:43
To: [email protected]
Subject: Uncaught exception: System.IndexOutOfRangeException

I'm using log4net 1.2.9 and got these uncaught exceptions thrown from my 
application causing it to crash this past weekend:

System.IndexOutOfRangeException: Probable I/O race condition detected while 
copying memory.

I am using log4net with an asp.net 1.1 web service, and am writing entries to 
the log for every request. This is on a windows 2003 server, using iis6, and 
web gardening is turned on, so multiple instances of w3wp.exe are running and 
processing requests.

Here is the full stack trace:
System.Web.Services.Protocols.SoapException: Server was unable to process 
request. ---> System.IndexOutOfRangeException: 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. at System.Buffer.InternalBlockCopy(Array src, Int32 srcOffset, 
Array dst,
Int32 dstOffset, Int32 count) at System.IO.StreamWriter.Write(Char[]
buffer, Int32 index, Int32 count) at
System.IO.TextWriter.WriteLine(String value) at 
System.IO.SyncTextWriter.WriteLine(String value) at 
log4net.Util.LogLog.Error(String message, Exception exception) at 
log4net.Util.AppenderAttachedImpl.AppendLoopOnAppenders(LoggingEvent
loggingEvent) at
log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent
loggingEvent) at log4net.Repository.Hierarchy.Logger.ForcedLog(Type
callerStackBoundaryDeclaringType, Level level, Object message, Exception 
exception) at log4net.Repository.Hierarchy.Logger.Log(Type
callerStackBoundaryDeclaringType, Level level, Object message, Exception 
exception) at log4net.Core.LogImpl.Error(Object message) at 
My.Online.App.Logger.Error(String msg) at
My.Online.App.ComcastMSOOffersService..ctor() --- End of inner exception stack 
trace ---


Thanks,
Michelle Weber

Reply via email to