logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Mazurskiy (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LOG4J2-981) Incorrect unlock in ProviderUtil
Date Sat, 21 Mar 2015 08:52:38 GMT

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

Mikhail Mazurskiy updated LOG4J2-981:
-------------------------------------
    Attachment: LOG4J2-981.patch

Attaching proposed patch.

> Incorrect unlock in ProviderUtil
> --------------------------------
>
>                 Key: LOG4J2-981
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-981
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.2
>            Reporter: Mikhail Mazurskiy
>            Priority: Trivial
>         Attachments: LOG4J2-981.patch
>
>
> {{org.apache.logging.log4j.util.ProviderUtil#lazyInit}} call can result in {{IllegalMonitorStateException}}
if thread is in interrupted state because code in the finally block will try to unlock the
lock that is not held by the current thread ({{InterruptedException}} thrown before the lock
is acquired).



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

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message