A-MQ 6.0 ran out of memory due to 1,333 Java threads consuming memory
Issue
We see 77% of threads of this type in TIMED_WAIT state:
"JMX server connection timeout 5093122" daemon prio=10 tid=0x00000000019ca000 nid=0x3407 in Object.wait() [0x00007f2088342000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00000000e26e9530> (a [I)
at com.sun.jmx.remote.internal.ServerCommunicatorAdmin$Timeout.run(ServerCommunicatorAdmin.java:168)
- locked <0x00000000e26e9530> (a [I)
at java.lang.Thread.run(Thread.java:722
And an equal number of:
"JMX client heartbeat 1820" daemon prio=10 tid=0x00007f20b03bf000 nid=0x111f waiting on condition [0x00007f208bc7b000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at com.sun.jmx.remote.internal.ClientCommunicatorAdmin$Checker.run(ClientCommunicatorAdmin.java:174)
at java.lang.Thread.run(Thread.java:722)
Environment
JBoss A-MQ 6.0.0
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.
