Bug 1697284 - [GSS] (6.4.z) REMJMX-160 - Every JMXConnectorFactory#connect() creates a new ThreadGroup which is never reclaimed
Summary: [GSS] (6.4.z) REMJMX-160 - Every JMXConnectorFactory#connect() creates a new ...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: JMX
Version: 6.4.21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: EAP 6.4.23
Assignee: Chao Wang
QA Contact: Peter Mackay
URL:
Whiteboard:
Depends On:
Blocks: eap6423-payload 1708467 1708707
TreeView+ depends on / blocked
 
Reported: 2019-04-08 09:39 UTC by Masafumi Miura
Modified: 2025-02-10 03:59 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:59:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-16685 0 Major Verified [GSS](7.2.z) REMJMX-160 - Every JMXConnectorFactory#connect() creates a new ThreadGroup which is never reclaimed 2020-10-14 10:16:23 UTC
Red Hat Issue Tracker REMJMX-160 0 Major Resolved Every JMXConnectorFactory#connect() creates a new ThreadGroup which is never reclaimed 2020-10-14 10:16:23 UTC
Red Hat Knowledge Base (Solution) 4054101 0 None None A memory leak happens in JMX Client application which repeats connecting and closing JMXConnector over remoting-jmx in J... 2019-05-10 12:07:29 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.