[ARTEMIS-2577] Thread leak test failure with IBM JRE

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.11.0
• Assignee: Unassigned
• Reporter: Domenico Francesco Bruscino
• Created: 16/Dec/19 13:27
• Updated: 10/Jan/20 17:38
• Resolved: 03/Jan/20 02:53

Description

The test suite checks thread leak after each test, checking all the running threads at the end of the test and if any of the thread is not in the expected set, the test will fail.

The expected set is a set of thread names that can be ignored when checking thread leak. With IBM jre, the broker will cause a daemon thread called "MemoryMXBean" to be started by the VM. This thread is not controlled by the broker and should be put to the expected set. Otherwise tests will report false thread leak error.

LEAKING THREADS
=============================================================================
Thread Thread[MemoryMXBean notification dispatcher,6,main] is still alive with the following stackTrace:
com.ibm.lang.management.internal.MemoryNotificationThread.processNotificationLoop(Native Method)
com.ibm.lang.management.internal.MemoryNotificationThread.run(MemoryNotificationThread.java:183)
*********************************************************************************
[main] 18:10:19,675 INFO  [org.apache.activemq.artemis.utils.ThreadLeakCheckRule] #test forceGC
[main] 18:10:19,777 INFO  [org.apache.activemq.artemis.utils.ThreadLeakCheckRule] #test forceGC Done 
*********************************************************************************

 

Issue Links

• is cloned by: ARTEMIS-2593 Thread leak test failure with OpenJ9 JVM
• links to: GitHub Pull Request #2919