OutOfMemoryError in JBoss A-MQ due to million instances of org.apache.activemq.thread.SchedulerTimerTask
Issue
Our A-MQ broker ran out of memory. We captured a JVM heap dump and its analysis shows million of instances of class org.apache.activemq.thread.SchedulerTimerTask.
These occupy 80 or more percent of the entire JVM heap.
Environment
- JBoss A-MQ 6.1.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.