Application has poor performance with threads blocking on Log4J2 handlers

Solution Unverified - Updated -


  • Applications using log4j2 appenders show poor performance due to threads blocking.

  • Call stack threads are "waiting on lock" leading to a log4j class.

  • Camel route applications become unresponsive while logging.

  • Threads wait long periods on locks for org.apache.logging.log4j.core.appender.OutputStreamManager.


  • Fuse 7.x on OpenShift 3.11

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In