[LOG4J2-1324] Install default error handler for Async Loggers that does not rethrow (was: Async Logger - Consumer thread dying - new thread unable to start)

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2
• Fix Version/s: 2.6
• Component/s: Core

Environment

LOG4J CORE Release Version 2.2
Disruptor Bundle-Version 3.3.2
ORACLE jdk1.8.0_45
Linux 2.6.32-573.el6.x86_64, amd64

• Assignee: Remko Popma
• Reporter: Steve Yurong Su
• Created: 21/Mar/16 16:44
• Updated: 26/Mar/16 05:07
• Resolved: 26/Mar/16 05:07

Description

We are seeing a situation where the consumer thread
"AsyncLoggerConfig-1" is apparently dying.
We do see a new consumer thread trying to start up, but it is blocked
waiting for a lock, so no logging is happening.

Is this a defect in log4j?
Is the original consumer thread dying due to perhaps an unhandled exception ?
Is that original consumer thread not terminating gracefully and
releasing the locked object so the new consumer thread can start?

Please see attached screenshot. Top of screen is normal
asyncloggerconfig thread (consumer).
Bottom is thread trace when logging stops, we no longer see an
"asyncloggerconfig-1" thread, instead a new thread is trying to start
but never does "asyncloggerconfig-2".