AEM GC overhead limit exceeded

[#1]

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!

[Tuhin_Ghosh]

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 · Accepted solution]

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-exceed...

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]

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]

Hi,

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

Thanks

Tuhin