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 of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.