My Oracle Support Banner

Memory Leak in java.util.HashMap$Entry[] and sun.misc.Launcher$AppClassLoader (Doc ID 1997902.1)

Last updated on SEPTEMBER 25, 2017

Applies to:

Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.

Symptoms

After migrating Web Service application from WLS 10.3.2 to 12.1.2, the JVM is running out of memory. WLS instances were originally configured with 1GB of heap but have since been increased to 2GB.  Servers still run out of memory after approximately 3 hours.  Heap dumps show single object that is labeled most likely leak suspect is:  

One instance of "com.sun.jmx.mbeanserver.JmxMBeanServer" loaded by "<system class loader>" occupies 130,139,536 (20.42%) bytes. The instance is referenced by weblogic.management.jmx.mbeanserver.WLSMBeanServer @ 0xc10fee10 , loaded by "sun.misc.Launcher$AppClassLoader @ 0xc0020588". The memory is accumulated in one instance of "java.util.HashMap$Entry[]" loaded by "<system class loader>".

 
Keywords
com.sun.jmx.mbeanserver.JmxMBeanServer
java.util.HashMap$Entry[]
sun.misc.Launcher$AppClassLoader @ 0xc0020588

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.