[LOG4J2-981] Incorrect unlock in ProviderUtil

• Type: Bug
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 2.2
• Fix Version/s: 2.3
• Component/s: Core
• Assignee: Unassigned
• Reporter: Mikhail Mazursky
• Created: 21/Mar/15 08:51
• Updated: 21/Mar/15 22:53
• Resolved: 21/Mar/15 18:17

Description

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).