J2EE Application Using Coherence as Hibernate L2 Cache Leaks Memory on MapEvent And Eventually Fails With OOME
Last updated on FEBRUARY 24, 2017
Applies to:Oracle Coherence - Version 220.127.116.11 and later
Information in this document applies to any platform.
In a WLS 10.3.6 environment with Coherence 18.104.22.168 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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms