Hi All,
We are using log4net in our multi threaded windows service since last 3
years or so. We have recently encountered that our device became
unresponsive/went into hanging state couple of time. While analyzing crash
dump of the service of that time, we have encountered that one of our thread
has failed during rolling file operation. The stack trace of failed thread
as follows :
log4net.Util.LogLog.EmitErrorLine(System.String)
log4net.Util.LogLog.Warn(System.Type, System.String)
log4net.Appender.RollingFileAppender.RollFile(System.String,
System.String)
log4net.Appender.RollingFileAppender.RollOverTime(Boolean)
log4net.Appender.RollingFileAppender.AdjustFileBeforeAppend()
log4net.Appender.RollingFileAppender.Append(log4net.Core.LoggingEvent)
log4net.Appender.AppenderSkeleton.DoAppend(log4net.Core.LoggingEvent)
....
....
While going through error thrown by above stack trace, we have encountered
following error message :
log4net:WARN Cannot RollFile [....] -> [....]. Source does not exist
All other threads are waiting at following log4net method :
log4net.Appender.AppenderSkeleton.DoAppend(log4net.Core.LoggingEvent)
log4net.Util.AppenderAttachedImpl.AppendLoopOnAppenders(log4net.Core.LoggingEvent)
....
....
Rolling File Pattern is as following :
<datePattern value=".yyyyMMdd-HH".log""/>
We are not able to understand what is exactly wrong over here which causes
service to become unresponsive. Does rolling file operation cause the
thread, which is using it, to go into unresponsive state if some error
occurs ? We have gone through other posts which are telling to use different
datepattern but changing datepattern is not solving problem for everybody.
We would like to know what is the full proof way to solve this issue.
Thanks.
--
View this message in context:
http://apache-logging.6191.n7.nabble.com/Rolling-File-Operation-Failing-with-Source-does-not-exist-tp62802.html
Sent from the Log4net - Users mailing list archive at Nabble.com.
