Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] frequently down

>> Take some heap dumps (preferably when you are close to out of memory)

There was a heap dump from the last OOM error linked in I had a look and posted some comments in the bug.

There are over a million of Jetty sessions, but I can’t tell yet why they are there (paths to them seem rather expected).


From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Matthias Sohn
Sent: Mittwoch, 17. August 2011 00:51
To: Cross project issues
Subject: Re: [cross-project-issues-dev] frequently down


2011/8/16 Denis Roy <denis.roy@xxxxxxxxxxx>


As you may know, lately we've been having issues with  The Indigo help center runs out of memory frequently, no matter how much we seem to give it, and it ends up dying.

We've opened up since we're assuming there is a memory leak somewhere.  In the grand scheme of things, the whole thing is just a bit embarrassing. Since we are by no means Java app troubleshooting experts, if anyone has any cycles to perhaps tell us how we can go about fixing this, it would be great.


you may use VisualVM [1] to monitor the running Java App. Connect to the JVM 

which runs the help center, if you do that from a different host follow [2]. The monitored 

process will appear in the tree on the left side. Double click it to open the monitoring 

views. Open the tab "Monitor", in the top right pane you can monitor the JVM heap. 

Take some heap dumps (preferably when you are close to out of memory). VisualVM 

will show on the next page where the heap dump is stored. 


Analyze the heap dump using Eclipse memory analyzer (MAT) [3]: install MAT into an 

Eclipse installation, open the "Memory Analysis" perspective and click "File > Open Heap Dump...", 

select the heap dump to initiate parsing the heap dump, this will take a couple of minutes. 

MAT will open the "Getting Started Wizard", select the "Leak Suspect Report" and click "Finish". 

This report should give you a rough overview on suspects for memory leaks in the application.




Back to the top