Financial Close Management JVM Crashing With Out Of Memory Errors - java.lang.OutOfMemoryError: GC overhead limit exceeded. (Doc ID 3009163.1)

Last updated on MARCH 12, 2024

Applies to:

Symptoms

Logs show:

java.lang.OutOfMemoryError: GC overhead limit exceeded.
java.lang.OutOfMemoryError: GC overhead limit exceeded
at weblogic.utils.UnsyncStringBuffer.ensureCapacity(UnsyncStringBuffer.java:66)
at weblogic.utils.UnsyncStringBuffer.append(UnsyncStringBuffer.java:125)
at weblogic.rjvm.JVMID.toString(JVMID.java:1124)
at java.lang.String.valueOf(String.java:2994)
at java.lang.StringBuilder.append(StringBuilder.java:137)
at weblogic.cluster.HybridClusterMessageReceiver.processLastSeqNum(HybridClusterMessageReceiver.java:66)
at weblogic.cluster.ClusterMessagesManager$2.run(ClusterMessagesManager.java:447)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:344)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:137)
at weblogic.cluster.ClusterMessagesManager.receiveHeartbeat(ClusterMessagesManager.java:413)
at weblogic.cluster.HeartbeatMessage.execute(HeartbeatMessage.java:33)
at weblogic.cluster.ClusterMessageReceiver$1.run(ClusterMessageReceiver.java:153)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:655)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:420)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:360)

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.