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

Memory Leak Analysis

  • May 25, 2017
  • 13 replies
  • 11926 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
smacdonald2008
smacdonald2008Accepted solution
New Participant
May 25, 2017

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

J
jocampAuthor
New Participant
May 25, 2017

Thanks for that, i did read through those earlier but they seem to end about where i am now. The examples i've found all have obvious leak suspects, such as a custom class, so i'm not sure how to handle the leak suspects being part of CQ's framework classes. It just seems like all HTTP/Servlet calls are causing memory leaks.

Terms & ConditionsAccessibility statement

Loading footer...