OOME from high heap retention in com.lmax.disruptor.RingBuffer with log4j2

Solution Unverified - Updated -

Issue

  • We hit a heap space OOME and see high heap retention from many log messages stored in com.lmax.disruptor.RingBuffer.

Environment

  • Java
  • Log4j2

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