Log4j NDC prevents proper GC of idle threads when using executors for web connector pools

Solution Unverified - Updated -

Issue

  • We have JBoss configured to use executors for the web connectors. The executors are configured with a keepalive-time to remove idle threads. We see a very large amount of threads in the heap, far greater than our configured max-threads. These trace back to a log4j NDC HashTable.

Environment

  • JBoss Enterprise Application Platform (EAP) 6
  • Apache log4j NDC

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

New to Red Hat?

Learn more about Red Hat subscriptions

Close

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