Thousands of org.slf4j.Logger instances in AMQ broker JVM heap dump, causing the broker JVM to eventually run out of memory
Issue
- The AMQ broker has suffered from OutOfMemoryError.
- The JVM heap dump shows tens of thousands (or more) instances of
org.slf4j.Logger.
Environment
- JBoss AMQ 6.3
transport.trace=trueadded to brokers transport connector, e.g
<transportConnector name="openwire"uri="tcp://0.0.0.0:61616?transport.trace=true"/>
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
