[LOG4J2-1518] Deadlock when using pure async and toString logs another message

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6.2
• Fix Version/s: 2.7

Environment

Solaris

• Assignee: Remko Popma
• Reporter: Leon Finker
• Created: 15/Aug/16 02:59
• Updated: 10/Sep/17 12:53
• Resolved: 05/Sep/16 18:00

Description

Hi,

It looks like this was reported before in: LOG4J2-471

We've encountered similar issue with one of the libraries where it's toString was indirectly also logging. This caused a deadlock when RingBuffer was full. Please see attached stack snippet.

According to the following docs, it's possible to set sync policy to synchronously log the event if buffer is full. I don't see it documented. What's the policy option?
https://issues.apache.org/jira/plugins/servlet/mobile#issue/LOG4J2-1080
https://logging.apache.org/log4j/2.x/log4j-core/apidocs/org/apache/logging/log4j/core/async/AsyncQueueFullPolicyFactory.html

Thank you

Issue Links

• breaks: LOG4J2-2031 Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)