My Oracle Support Banner

Coherence JMX Management Node In A Large Cluster Crashes With An OutOfMemoryError (Doc ID 1531005.1)

Last updated on SEPTEMBER 18, 2018

Applies to:

Oracle Coherence - Version 3.7.1.6 and later
Information in this document applies to any platform.

Symptoms

A large cluster is configured with a dedicated JMX Management node, which crashes due to an OutOfMemoryError exception.  The node is configured with a custom cache configuration file to ensure that it does not join any cache services and that it only starts the invocation service as that is used internally by the Coherence management infrastructure:

<cache-config>
   <caching-schemes>
       <invocation-scheme>
           <service-name>Dummy</service-name>
           <autostart>true</autostart>
       </invocation-scheme>
   </caching-schemes>
</cache-config>

The management node is configured to dump its heap on an OutOfMemoryError with the flags:

-XX:HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/path/to/dumpfile.hprof

Analysing the heap dump captured with a utility such as the Eclipse Memory Analyzer reports the leak suspect:

28,060 instances of "com.tangosol.coherence.component.net.management.model.RemoteModel", loaded by "sun.misc.Launcher$AppClassLoader @ 0x24975800" occupy 2,838,055,592 (85.94%) bytes. These instances are referenced from one instance of "com.tangosol.util.SafeHashMap$Entry[]", loaded by "sun.misc.Launcher$AppClassLoader @ 0x24975800"

Keywords
com.tangosol.coherence.component.net.management.model.RemoteModel
sun.misc.Launcher$AppClassLoader @ 0x24975800
com.tangosol.util.SafeHashMap$Entry[]

 

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
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.