GC overhead limit exceeded | Community
Skip to main content
Siva_Sogalapalli
Community Advisor
Siva_SogalapalliCommunity Advisor
Community Advisor
October 16, 2015
Solved

GC overhead limit exceeded

  • October 16, 2015
  • 1 reply
  • 1447 views

AME stops responding when we get Out of memory issue:

Log Details: 08.05.2015 02:57:23.899 *ERROR* [10.9.91.251 [1431070180006] HEAD /libs/granite/core/content/login.html HTTP/1.1] org.apache.sling.servlets.resolver.internal.SlingServletResolver Original error class java.lang.Exception java.lang.Exception: Wrapping Throwable: java.lang.OutOfMemoryError: GC overhead limit exceeded

Please suggest me what could be the reasons and how to fix it.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

Hi,

it looks like you have a memory leak in your application. A good starter how to debug this can be found on [1]. The procedure to debug such memory problems is not specific to AEM.

kind regards,
Jörg

ps: The only way to create a memory leak with AEM specifics (at least known to me) is not to close JCR sessions and Sling ResourceResolvers. But with recent versions of AEM you should have lots of warnings about this in your logs.

[1] http://www.oracle.com/technetwork/java/javase/memleaks-137499.html

1 reply

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

Hi,

it looks like you have a memory leak in your application. A good starter how to debug this can be found on [1]. The procedure to debug such memory problems is not specific to AEM.

kind regards,
Jörg

ps: The only way to create a memory leak with AEM specifics (at least known to me) is not to close JCR sessions and Sling ResourceResolvers. But with recent versions of AEM you should have lots of warnings about this in your logs.

[1] http://www.oracle.com/technetwork/java/javase/memleaks-137499.html

Terms & ConditionsAccessibility statement

Loading footer...