Bug 1264555 - (6.4.z) Memory leak in remoting-jmx : https://issues.jboss.org/browse/REMJMX-94
Summary: (6.4.z) Memory leak in remoting-jmx : https://issues.jboss.org/browse/REMJMX-94
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: JMX
Version: 6.4.3
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: ---
Assignee: baranowb
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1191002
TreeView+ depends on / blocked
 
Reported: 2015-09-18 19:31 UTC by Simeon Pinder
Modified: 2016-09-19 07:58 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: http://bugs.java.com/view_bug.do?bug_id=6543126 Consequence: The issue doesn't really have a workaround. The logmanager, or possibly in this case jboss-client.jar as it shades in the logmanager, needs to be loaded by the same class loader each time. Creating a new class loader to load the library each time will always result in a memory leak. Fix: No possible Result: JDK8+ should fix the problem
Clone Of: 1191002
Environment:
Last Closed: 2016-09-19 07:58:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-710 0 Major Reopened Memory leak in remoting-jmx : https://issues.jboss.org/browse/REMJMX-94 2019-07-29 09:45:15 UTC
Red Hat Issue Tracker REMJMX-94 0 Major Open Memory leak in remoting-jmx 2019-07-29 09:45:15 UTC


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