]
Adrián López updated JBREM-1340:
--------------------------------
Attachment: img-2019-04-01-130952.png
Memory leak related to org.jboss.threads.JBossThreadFactory
-----------------------------------------------------------
Key: JBREM-1340
URL:
https://issues.jboss.org/browse/JBREM-1340
Project: JBoss Remoting
Issue Type: Bug
Components: jmx remoting
Reporter: Adrián López
Priority: Major
Attachments: img-2019-04-01-130952.png
We have a memory leak when using the jboss-cli-client JAR inside of Jolokia.
Jolokia uses remoting to connect to the JMX of several JBoss servers. After running for
some days, the Old Gen memory space reach 100%.
A heap dump analyzed with Eclipse MAT returns:
{code}
One instance of "java.lang.ThreadGroup" loaded by "<system class
loader>" occupies 377.517.248 (87,28%) bytes. The instance is referenced by
org.jboss.threads.JBossThread @ 0xe0a81ef0 HTTP-11 , loaded by
"org.jboss.modules.ModuleClassLoader @ 0xe04ffe20". The memory is accumulated in
one instance of "java.lang.ThreadGroup[]" loaded by "<system class
loader>".
The stacktrace of this Thread is available. See stacktrace.
Keywords
java.lang.ThreadGroup[]
org.jboss.modules.ModuleClassLoader @ 0xe04ffe20
java.lang.ThreadGroup
{code}
I have created also another [
issue|https://issues.jboss.org/browse/JBTHR-72] to
jboss-threads, but looks the problem is not there.
Same for [
Jolokia|https://github.com/rhuss/jolokia/issues/401]
Thanks