Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

GC overhead limit exceeded

Avatar

Community Advisor

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.

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

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

View solution in original post

1 Reply

Avatar

Correct answer by
Employee Advisor

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