Application has poor performance with threads blocking on Log4J2 handlers

Solution Unverified - Updated -

Issue

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

Environment

  • Fuse 7.x on OpenShift 3.11

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content