java.lang.OutOfMemoryError: GC overhead limit exceeded

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by Nir, 1 year ago
via GitHub by dahaian
, 1 month ago
GC overhead limit exceeded
via Oracle Community by 542526, 3 months ago
java.lang.OutOfMemoryError: GC overhead limit exceeded
at java.lang.Integer.toString(Integer.java:308)
at java.lang.Integer.toString(Integer.java:118)
at java.lang.String.valueOf(String.java:2931)
at com.octetstring.vde.util.Logger.alog(Logger.java:302)
at com.octetstring.vde.MessageHandler.doModify(MessageHandler.java:301)
at com.octetstring.vde.MessageHandler.answerRequest(MessageHandler.java:76)
at com.octetstring.vde.WorkThread.executeWorkQueueItem(WorkThread.java:86)
at weblogic.ldap.LDAPExecuteRequest.run(LDAPExecuteRequest.java:50)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Know the solutions? Share your knowledge to help other developers to debug faster.