You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4net-dev@logging.apache.org by "Stefan Bodewig (JIRA)" <ji...@apache.org> on 2016/10/15 16:10:20 UTC

[jira] [Resolved] (LOG4NET-512) Thread safety issue in Hierarchy.cs

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

Stefan Bodewig resolved LOG4NET-512.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.6

should be fixed with an adapted version of your patch as svn revision 1765091

Many thanks!

> Thread safety issue in Hierarchy.cs
> -----------------------------------
>
>                 Key: LOG4NET-512
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-512
>             Project: Log4net
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.15
>            Reporter: Joe
>            Priority: Minor
>             Fix For: 2.0.6
>
>
> From inspecting the source code I believe there is a threading bug in the Hierarchy class.  Both of the methods Exists and GetCurrentLoggers access the internal hashtable m_ht without locking.
> Impact is minor as both these methods are probably rarely called by third party code, and since they do not modify state, the worst that can happen is an unexpected exception.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)