Memory Leak Analysis | Community
Skip to main content
J
jocamp
Level 3
May 25, 2017
Solved

Memory Leak Analysis

  • May 25, 2017
  • 13 replies
  • 11935 views

Hello,

We've had memory leak issues for a while that will eventually push our publishers into 100% GC after a week or two. Up until now we've just been ignoring them because it's easier to restart the publisher but i would like to really understand how to troubleshoot this. We have a heap dump but what i'm seeing doesn't seem that helpful. All of the classes it references are framework classes, so i'm not sure how to proceed in finding the actual cause of the leak in our code. Below is the main leak suspect "HttpListener" loaded by "BundleWiringImpl" -

There are hundreds of these instances, each with a URL that is called by the end user. The below example is a keepalive call to a static html page, so none of our custom code should even be running.

Does anyone have suggestions on how to proceed here? Every time we take a heap dump the problem suspects are from "org.apache.felix.framework.BundleWiringImpl$BundleClassLoaderJava", "com.day.j2ee.servletengine.HttpListener", and "com.day.j2ee.servletengine.ServletHandlerImpl".

We are still on 5.6.1

 

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 smacdonald2008

I would recommend opening a ticket - there may be a required hotfix. Looks like some sort of bug and the support team can help. 

13 replies

Show previous replies
C
cmr96960454
Level 2
August 22, 2019

Hi Team,

We are also facing similar issues.

Everyday we are seeing publisher 1 or publisher 2 having issues (Major issue is old generation space reached 100% )and due to this admin is just restarting the instances.

Below is the link for head dump analysis.

https://fastthread.io/my-thread-report.jsp?p=c2hhcmVkLzIwMTkvMDgvMjIvLS1qc3RhY2suMTU0NDguMTAxMzEwLjc0OTQ2MTMwOS0tNi01Ni00MTs7LS1qc3RhY2suMTU0NDguMTAxNjEzLjQwODc4OTg0NC0tNi01Ni00MTs7LS1qc3RhY2suMTU0NDguMTAxNjI0LjMwNjQ0MDMyNS0tNi01Ni00MTs7LS1qc3RhY2suMTU0NDguMTAxNjAxLjM5NzQ3MjQ1MS0tNi01Ni00MTs7LS1qc3RhY2suMTU0NDguMTAxNjMyLjA1OTU2MDA0Ni0tNi01Ni00MQ

This may be the memory issue but we don't have clues in application. Someone please verify link and suggest.

V
Adobe Employee
vish.dhaliwalAdobe Employee
Adobe Employee
August 22, 2019

Hello,

For memory-related issues, you should also take a heap dumps along with thread dumps. The link that you have provided is for thread dumps, not heap dumps.

Follow the link [1] to see instructions to take heap dumps. Also, review the memory usage here: http://aem-host:port/system/console/memoryusage screen

I suggest you open a Daycare ticket and provide heap dumps, thread dumps, aem logs etc for analysis.

[1] Analyze Memory Problems

V
Adobe Employee
vish.dhaliwalAdobe Employee
Adobe Employee
August 22, 2019

Here is another very good article: Common critical AEM issues

Terms & ConditionsAccessibility statement

Loading footer...