Deadlock in Apache log4j

Solution Verified - Updated

Environment

  • JBoss Enterprise Application Platform
    • 4.3.x
    • 5.x

Issue

  • Thread dump shows a deadlock involving log4j org.apache.log4j.spi.RootLogger.

Resolution

Replace the AsyncAppender with a FileAppender. See the following document for how to do this on JBoss EAP: How do I replace the AsyncAppender with a FileAppender on JBoss?

Root Cause

The AsyncAppender is known to cause performance issues and deadlocks in some situations.

Diagnostic Steps

Check the stack trace for AsyncAppender use.

Components
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.