Domenico Bruscino created ARTEMIS-2593:
------------------------------------------
Summary: Thread leak test failure with OpenJ9 JVM
Key: ARTEMIS-2593
URL: https://issues.apache.org/jira/browse/ARTEMIS-2593
Project: ActiveMQ Artemis
Issue Type: Bug
Reporter: Domenico Bruscino
Fix For: 2.11.0
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.
{code}
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
*********************************************************************************
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
