Coherence Member Crashes Throwing Java.Lang.OutOfMemoryError: Direct Buffer Memory
(Doc ID 1465171.1)
Last updated on NOVEMBER 09, 2022
Applies to:Oracle Coherence - Version 3.7.1 and later
Information in this document applies to any platform.
In a Standalone Coherence Cluster or FMW WebLogic Domains coherence process is getting stopped/ejected from the coherence cluster due to java.lang.OutOfMemoryError: Direct buffer memory error.
Coherence does use byte buffers. In this case coherence member was Out Of JVM Heap Space and failed to create (Direct/off-heap) NIO byte buffer. Coherence proxy members' TCP connection acceptor failed to process requests because it could not create/allocate buffer pool required. That was the reason for the coherence proxy member got stopped its TCPAcceptor service - due to unhandled exception: jjava.lang.OutOfMemoryError: Direct buffer memory.
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