[
https://issues.apache.org/jira/browse/LOG4NET-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4NET-616:
--------------------------------
LOG4NET is now dormant.
> NullReferenceException in FileAppender.LockingModelBase.CloseStream method
> --------------------------------------------------------------------------
>
> Key: LOG4NET-616
> URL: https://issues.apache.org/jira/browse/LOG4NET-616
> Project: Log4net
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.0.8
> Reporter: Frank Nietzold
> Priority: Major
>
> We are using log4net in a multithreaded application. When running the
> application from Visual Studio with debugging, in rare occasions a
> NullReferenceException occurs in FileAppender.LockingModelBase in the
> CloseStream method:
> System.NullReferenceException: Object reference not set to an instance of an
> object.
> at log4net.Appender.FileAppender.LockingModelBase.CloseStream(Stream stream)
> at log4net.Appender.FileAppender.MinimalLock.ReleaseLock()
> at log4net.Appender.FileAppender.LockingStream.ReleaseLock()
> at log4net.Appender.FileAppender.CloseWriter()
> at log4net.Appender.TextWriterAppender.Reset()
> at log4net.Appender.FileAppender.Reset()
> at log4net.Appender.TextWriterAppender.OnClose()
> at log4net.Appender.FileAppender.OnClose()
> at log4net.Appender.AppenderSkeleton.Close()
> at log4net.Appender.AppenderSkeleton.Finalize()
> at log4net.Appender.RollingFileAppender.Finalize()
>
> Debugging with log4net source code revealed it's the stream parameter of the
> CloseStream method that is null. Without knowing the root cause why the value
> is already null here (shouldn't be the case), would it be possible to add a
> null check here?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
