OutOfMemoryError Thrown By Coherence Nodes If -Xprof Is Used

(Doc ID 1237163.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Coherence - Version: 3.5.2 and later   [Release: AS10g and later ]
Information in this document applies to any platform.


Coherence cluster nodes run into OutOfMemoryError after some days if the java option "-Xprof" is used.

The following manual recommends to use the java option "-Xprof"
Oracle Coherence Getting Started Guide Release 3.5, 20 Best Practices, Heap Size Considerations

For allocation-intensive code, GC can theoretically consume close to 100% of CPU usage. For both cache server and client configurations, most CPU resources will typically be consumed by application-specific code. It may be worthwhile to view verbose garbage collection statistics (for example, -verbosegc). Use the profiling features of the JVM to get profiling information including CPU usage by GC (for example, -Xprof).


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