[
https://issues.apache.org/jira/browse/LOG4NET-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davyd McColl closed LOG4NET-510.
--------------------------------
Resolution: Fixed
Hi
In a bid to get the machinery all going again, I'm closing out old issues,
especially when:
- they are against older versions of log4net ( < 2)
- they have no associated pull request
- they are unlikely to receive attention because they're wishlist material
I'm doing this to try to increase the signal-to-noise ratio so that it's more
likely
that issues which can be attended to get the attention they deserve.
I'm not doing this because your contribution isn't important. On the contrary,
if
the problem still persists, please raise a new issue -- I'd like to know about
it.
> FileAppender.InterProcessLock.AcquireLock blocks everything
> -----------------------------------------------------------
>
> Key: LOG4NET-510
> URL: https://issues.apache.org/jira/browse/LOG4NET-510
> Project: Log4net
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 1.2.13
> Environment: Windows 2012
> Reporter: StevenXi
> Priority: Critical
> Attachments: screenshot-1.png
>
>
> There's a chance InterProcessLock.AcquireLock hangs, and lots of
> Appender.AppenderSkeleton.DoAppend threads queued.
> It happens to our service every 2 days, all happen after mid-night. So after
> a new log file created, few new line in the file added. But not always
> happens.
> As there're hundreds of Appender.AppenderSkeleton.DoAppend threads queued, it
> blocks everywhere in the service that uses log4net.
> log4net is supposed to be 'failure-free' or at least fails quietly, not block
> the whole application.
> config uses
> <lockingModel type="log4net.Appender.FileAppender+InterProcessLock" />
> So far it has hanged for few (8+) hours already.
> The attached screen shot was taken by remote debug from a server after 8+
> hours of hanging.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
