Bug 1150304

Summary: JMX monitoring is extremely memory inefficient
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Aaron Ogburn <aogburn>
Component: JMXAssignee: Brian Stansberry <brian.stansberry>
Status: CLOSED CURRENTRELEASE QA Contact: Jan Martiska <jmartisk>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3.2, 6.4.0CC: brian.stansberry, hrupp, kkhan, myarboro, pslavice
Target Milestone: DR7   
Target Release: EAP 6.4.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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: 1154868    

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.