OutOfMemoryError Exceptions During Startup Of Large Cluster Using Well Known Addressing (WKA)
(Doc ID 1463126.1)
Last updated on FEBRUARY 16, 2024
Applies to:
Oracle Coherence - Version 3.7.1 to 3.7.1.4 [Release AS10g]Information in this document applies to any platform.
Symptoms
You encounter an OutOfMemoryError exception during the startup of one or more of the nodes in your cluster. For example:
In the above example 95% of the heap is being consumed by an instance of the com.tangosol.coherence.component.net.Cluster$PacketSpeaker$BundlingQueue, however its equally possible that other elements of the PacketSpeaker could be where the memory is being accumulated, for example in the com.tangosol.coherence.component.net.Cluster$PacketReceiver$InQueue.
Changes
This issue can be encountered in Coherence for Java 3.7.1
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 |