AEM GC overhead limit exceeded | Community
Skip to main content
A
Anonymous
May 2, 2016
Solved

AEM GC overhead limit exceeded

  • May 2, 2016
  • 4 replies
  • 8233 views

Regarding error log attached, our AEM services had stopped working and had to be restarted.

We uploaded about 2000 xml files with about 5000 jpgs, only couple mb in size for the jpgs.

Only workflows that were running was DAM Update Asset. Suspect a memory leak some how from the error log.

Anyone shed some light on this? Thanks!

    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 kautuk_sahni

    Hi

    This message means that for some reason the garbage collector is taking an excessive amount of time (by default 98% of all CPU time of the process) and recovers very little memory in each run (by default 2% of the heap).

    This effectively means that your program stops doing any progress and is busy running only the garbage collection at all time.

    Link:- http://stackoverflow.com/questions/1393486/error-java-lang-outofmemoryerror-gc-overhead-limit-exceeded

    Link:- http://stackoverflow.com/questions/5839359/java-lang-outofmemoryerror-gc-overhead-limit-exceeded

     

    Adding reference KB articles:

    Link:- https://helpx.adobe.com/experience-manager/kb/thread-dumps-collection-analysis.html

    //Thread Dumps Collection and Analysis tool

    Link:- https://helpx.adobe.com/experience-manager/kb/TakeThreadDump.html

    //Take thread dumps from a JVM

    Link:- https://helpx.adobe.com/experience-manager/kb/AnalyzeMemoryProblems.html

    //Analyze Memory Problems

    I hope this will act as some help to you.

    Thanks and Regards

    Kautuk Sahni

    4 replies

    Tuhin_Ghosh
    Tuhin_Ghosh
    Level 8
    May 2, 2016

    Analyze the thread dump and see what is causing this problem. You could use samurai for the same. Here is an article stating about the debug process for your problem.

    http://www.aemcq5tutorials.com/tutorials/create-and-analyse-heap-dump-aem/

     

    Thanks

    Tuhin

      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity ManagerAccepted solution
      Community Manager
      May 3, 2016

      Hi

      This message means that for some reason the garbage collector is taking an excessive amount of time (by default 98% of all CPU time of the process) and recovers very little memory in each run (by default 2% of the heap).

      This effectively means that your program stops doing any progress and is busy running only the garbage collection at all time.

      Link:- http://stackoverflow.com/questions/1393486/error-java-lang-outofmemoryerror-gc-overhead-limit-exceeded

      Link:- http://stackoverflow.com/questions/5839359/java-lang-outofmemoryerror-gc-overhead-limit-exceeded

       

      Adding reference KB articles:

      Link:- https://helpx.adobe.com/experience-manager/kb/thread-dumps-collection-analysis.html

      //Thread Dumps Collection and Analysis tool

      Link:- https://helpx.adobe.com/experience-manager/kb/TakeThreadDump.html

      //Take thread dumps from a JVM

      Link:- https://helpx.adobe.com/experience-manager/kb/AnalyzeMemoryProblems.html

      //Analyze Memory Problems

      I hope this will act as some help to you.

      Thanks and Regards

      Kautuk Sahni

      Kautuk Sahni
        A
        Anonymous
        May 3, 2016

        Thanks for the replies all, this will surely help. But I guess I'm going to have to get the thread dump when the problem occurs again since

        AEM services have been restarted already now. 

        Tuhin_Ghosh
        Tuhin_Ghosh
        Level 8
        May 4, 2016

        Hi,

        Please close this ticket and mark this as solved you have satisfactory answers to your query.

        Thanks

        Tuhin

        Terms & ConditionsAccessibility statement

        Loading footer...