You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ralph Goers (Jira)" <ji...@apache.org> on 2020/04/04 22:31:01 UTC

[jira] [Updated] (LOG4NET-431) The AppenderSkeleton.DoAppend methods may cause deadlocks

     [ https://issues.apache.org/jira/browse/LOG4NET-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralph Goers updated LOG4NET-431:
--------------------------------

LOG4NET is now dormant.  

> The AppenderSkeleton.DoAppend methods may cause deadlocks
> ---------------------------------------------------------
>
>                 Key: LOG4NET-431
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-431
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>            Reporter: Fyodor Soikin
>            Priority: Major
>
> The AppenderSkeleton.DoAppender method calls a few methods (in particular, FilterEvent, PreAppendCheck, and Append), which are virtual.
> Calling code you don't control from within a synchronization block is a major no-no, thread-safely speaking. It may cause deadlocks - and, in my case, does cause them.
> In my particular case, the runaway code path starts with calling .ToString() on one of the format arguments. That particular argument is a complex object, whose ToString() implementation calls a few other components, some of which also use [poorly designed] synchronization constructs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)