Bug 1150304 - JMX monitoring is extremely memory inefficient
Summary: JMX monitoring is extremely memory inefficient
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: JMX
Version: 6.3.2,6.4.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: DR7
: EAP 6.4.0
Assignee: Brian Stansberry
QA Contact: Jan Martiska
URL:
Whiteboard:
Depends On:
Blocks: 1154868
TreeView+ depends on / blocked
 
Reported: 2014-10-07 21:31 UTC by Aaron Ogburn
Modified: 2019-08-19 12:46 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-3889 0 Major Resolved JMX monitoring is extremely memory inefficient 2016-09-28 16:15:14 UTC

Description Aaron Ogburn 2014-10-07 21:31:37 UTC 
Description of problem:

EAP 6 is susceptible to https://issues.jboss.org/browse/WFLY-3889 and needs a fix
Comment 3 Jan Martiska 2014-11-04 11:03:57 UTC 
Verified in EAP 6.4.0.DR7. The number of ModelNode instances created for every JMX attribute read dropped from ~6000 to ~1000. Used jvisualvm to measure this.
Note You need to log in before you can comment on or make changes to this bug.