Transactional Cache Node is Hung And Response is Slow due to OOM
(Doc ID 2692613.1)
Last updated on JUNE 07, 2022
Applies to:
Oracle Coherence - Version 12.1.3.0.0 and laterInformation in this document applies to any platform.
Symptoms
The Coherence cache node is hung and response is slow. Heap memory is getting full and causing OutOfMemory.
Example Architecture details:
There are 10 cache node of 3 GB each (3*10= Total 30 GB) and using Transactional cache for storing and manipulating cache object.
Observed that all of the cache nodes are running out 98% heap utilization and CPU is busy in running GC activity resulting the query run on cache cluster to be returning slow response. The cache node keeps complaining about communication delay even when all nodes are running on same server.
Changes
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 |
Changes |
Cause |
Solution |
References |