OutOfMemoryError Exceptions During Startup Of Large Cluster Using Well Known Addressing (WKA)
Last updated on SEPTEMBER 07, 2017
Applies to:Oracle Coherence - Version 3.7.1 to 188.8.131.52 [Release AS10g]
Information in this document applies to any platform.
***Checked for relevance on 21-Nov-2013***
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.
This issue can be encountered in Coherence for Java 3.7.1
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