Essbase 21c Independent Deployment: JVM Keeps Crashing error: With GC overhead limit exceeded.
(Doc ID 3043145.1)
Last updated on AUGUST 22, 2024
Applies to:
Hyperion Essbase - Version 21.1.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
JVM Keeps Crashing error: With GC overhead limit exceeded.
From Jagent.log:
<Apr 1, 2024 12:58:08,114 PM EDT> <Warning> <Socket> <BEA-000449> <Closing the socket, as no data read from it on **.**.**.***:**, *** during the configured idle timeout of 5 seconds.>
java.lang.OutOfMemoryError: GC overhead limit exceeded
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 |
Cause |
Solution |
References |