Bug 1697284

Summary: [GSS] (6.4.z) REMJMX-160 - Every JMXConnectorFactory#connect() creates a new ThreadGroup which is never reclaimed
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Masafumi Miura <mmiura>
Component: JMXAssignee: Chao Wang <chaowan>
Status: CLOSED UPSTREAM QA Contact: Peter Mackay <pmackay>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.21CC: acai, bmaxwell, chaowan, hrupp, igueye, jboss-set, pmackay, rpelisse
Target Milestone: ---   
Target Release: EAP 6.4.23   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:59:42 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:
Bug Depends On:    
Bug Blocks: 1699388, 1708467, 1708707    

Description Masafumi Miura 2019-04-08 09:39:05 UTC 
Description of problem:
See https://issues.jboss.org/browse/REMJMX-160 for details

Version-Release number of selected component (if applicable):
remoting-jmx 1.1.3.Final

How reproducible:
Anytime

Steps to Reproduce:
See steps to reproduce in https://issues.jboss.org/browse/REMJMX-160 for details. (As EAP 6 uses remoting-jmx protocol, you need to modify url from "service:jmx:remote+http://..." to  "service:jmx:remoting-jmx://..." in the reproducer.)
Comment 7 Peter Mackay 2020-06-30 11:48:45 UTC 
Verified with EAP 6.4.23.CP.CR2
Comment 9 Red Hat Bugzilla 2025-02-10 03:59:42 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.