[jira] [Commented] (LOG4NET-510) FileAppender.InterProcessLock.AcquireLock blocks everything

["Gregory Zak (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4NET-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383010#comment-15383010 ] 

Gregory Zak commented on LOG4NET-510:
-------------------------------------

Just wanted to add to this: I can consistently reproduce a hang by restricting the log folder such that the application doesn't have write permission and deleting the log file itself, then running the application normally.

When it tries to create the file for the first time, presumably it silently fails the first time due to permission issues, which is good. But any subsequent log attempts hang indefinitely.

> 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
(v6.3.4#6332)