Bug 1120177

Summary: controller client has a small memory leak as it's not cleaning up the ThreadGroup object
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Tom Fonteyne <tfonteyn>
Component: Domain ManagementAssignee: Brian Stansberry <brian.stansberry>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Kremensky <pkremens>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.3.0CC: dandread, kkhan, roland.raez
Target Milestone: DR1   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 12:38:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
reproducer none

Description Tom Fonteyne 2014-07-16 10:58:58 UTC
Created attachment 918390 [details]
reproducer

org.jboss.as.controller.client.impl.ClientConfigurationImpl

052 static ExecutorService createDefaultExecutor() {
053 final ThreadGroup group = new ThreadGroup("management-client-thread");

The ThreadGroup is never cleaned up and creates a memory leak

Reproducing:

Start an out of the box build. I used a snapshot EAP 6.3 build of July 9th.

Run the attached standalone program. It will do a loop creating a connection, and destroying it (try-with-resources)

When it display 240.000 take a heap dump. The dump will contain an equal amount of ThreadGroup objects as connections have been made.

The program will show memory calculations. These are not very precise of course, but the heap dump is very clear.

Comment 3 Petr Kremensky 2014-09-22 14:14:30 UTC
Verified on EAP 6.4.0.DR1.1