OutOfMemoryError When Coherence Logger Gets Stuck

(Doc ID 1456791.1)

Last updated on FEBRUARY 24, 2017

Applies to:

Oracle Coherence - Version 3.5.3 to [Release AS10g]
Information in this document applies to any platform.


Coherence nodes appear to leak memory when configured logger is stuck and stops processing messages.  The queue for the logger grows causing OOM errors.

Coherence nodes would finally crash and write a heap dump if configured as recommended.

A heap dump analysis would show the following dependency tree responsible for the heap consumption:






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