Troubleshooting a Memory Heap Dump to Identify Root Cause of Memory Leak - Example w/ oracle.dms.jmx.MetricMBeanInfo Accumulating Memory in java.util.HashMap
(Doc ID 2242825.1)
Last updated on MARCH 05, 2021
Applies to:Oracle WebLogic Server - Version 10.3.2 and later
Oracle Fusion Middleware - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
-- Applies to Oracle Weblogic Server
-- DMS is a Fusion Middleware component installed with WebLogic Server
-- Sample shown using DMS objects for troubleshooting but root cause is not due to DMS
This document provides steps to identity root cause of WLS jvm memory leak.
The sample leak suspect used in this note is oracle.dms.jmx.MetricMBeanInfo as reported in Eclipse Memory Analyzer(MAT) Problem Suspect page showing memory accumulated in one instance of java.util.HashMap$Entry :
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document