OutOfMemoryError Caused by Invoking Clear() on a Coherence Cache
(Doc ID 1541944.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Coherence - Version 3.5.3 and later
Information in this document applies to any platform.
***Checked for relevance on 04-Apr-2017***
***Checked for relevance on 10-Sep-2018***
Coherence nodes report an OutOfMemoryError exception after clear() has been invoked on a cache, typically a partitioned or external cache. Symptoms can vary, and the exception stack trace reported is not necessarily directly connected to the cause of the problem.
Another common symptom will be an increase in the amount of garbage collection (GC) activity each node is forced to perform, which will be reflected in any configured GC logging. If the nodes have not been tuned appropriately, and the GC activity is a "stop the world" collection, then communication delays will start to reported by the nodes in the cluster.
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