OutOfMemoryError When Coherence Logger Gets Stuck
(Doc ID 1456791.1)
Last updated on SEPTEMBER 15, 2022
Applies to:Oracle Coherence - Version 3.5.3 to 220.127.116.11 [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:
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