My Oracle Support Banner

J2EE Application Using Coherence As Hibernate L2 Cache Leaks Memory On MapEvent And Eventually Fails With OOME (Doc ID 1492669.1)

Last updated on FEBRUARY 03, 2019

Applies to:

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

Symptoms

In a WLS 10.3.6 environment with Coherence 3.7.1.5 using Coherence as a L2 Cache for Hibernate, there is an OOME (java.lang.OutOfMemoryError) reported after 3-4 days of operation. There is a very clear memory leak caused by com.tangosol.coherence.component.net.Member.

There are three instances of this class use 91% of the WLS heap. Each instance of com.tangosol.coherence.component.net.Member contains in turn around 20000 instances each of com.tangosol.coherence.component.util.daemon.queueProcessor , service , grid.partitionedService.PartitionedCache$MapEvent.

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.