RE: Memory Leak due to CMS

On Fri, 2005-02-18 at 17:06 +0530, Sukesh Shetty wrote:
> Mr David Matthew,
Matt ;)

> 
> Thanks for the response.I downloaded HeapWizard.jar but I'm not able to
> debug the source of the memory leak.We are using tomcat server for our
> application and due to memory leak problem we are rebooting our server
> every alternate days.
> Can you please give some guidelines regarding how to use HeapWizard.

IBM has excellent documentation. You'll need to look up the specifics
yourself, but in short:

You must obviously use the IBM JDK.
Set the environment variable IBM_HEAPDUMP=true
When your server runs out of memory, it will create a file containing
the heap dump. It should tell you about this in one of your log files
(wherever stderr goes, probably).
Find the HeapRoots tool (http://www.alphaworks.ibm.com/tech/heaproots)
to analyze this file.
It is also possible to signal the JVM to generate a heapdump immediately
without exiting.

Look for large, similar allocations of memory, probably attached to a
single structure. Chances are that even if there is more than one memory
leak that one is by far the biggest at the time you get OOM.

Matt

> 
> Thanks,
> Sukesh Shetty
> 
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Matthew David
> Booth
> Sent: Friday, February 18, 2005 3:46 PM
> To: [email protected]
> Subject: RE: [redhat-ccm-list] Memory Leak due to CMS
> 
> Hmm, I don't think we've fixed any memory leaks since 1.0.1. Using
> source is unlikely to be a problem.
> 
> I would very much appreciate it if you were able to debug the source of
> the memory leak. Some tools we've found helpful in the past have been
> the heapdump feature of IBM jdks
> (http://www-1.ibm.com/support/docview.wss?uid=swg24004782) and java
> debugging tools such as OptimizeIt. In practise, heapdump has been the
> most useful. If you can show me a section of heap which grows and what
> it contains, I should be able to fix the problem.
> 
> Matt
> 
> On Fri, 2005-02-18 at 15:20 +0530, Sukesh Shetty wrote:
> > Mr Matt,
> > Thanks for the response, yes we are using latest version of aplaws ie 
> > "aplaws-plus-src-1.0.1".
> > Is using source instead of rpm creating this problem?
> > 
> > Thanks,
> > Sukesh Shetty
> > 
> > -----Original Message-----
> > From: [email protected]
> > [mailto:[email protected]] On Behalf Of Matthew David
> 
> > Booth
> > Sent: Friday, February 18, 2005 2:46 PM
> > To: [email protected]
> > Subject: Re: [redhat-ccm-list] Memory Leak due to CMS
> > 
> > Have you tried running CMS and WAF from APLAWS
> (aplaws.sourceforge.net).
> > We've fixed a couple of memory leak bugs in there, and it could be 
> > that your problem has been fixed.
> > 
> > Matt
> > 
> > On Fri, 2005-02-18 at 12:36 +0530, Sukesh Shetty wrote:
> > > Hi All,
> > > 
> > > We are using CMS 6.1 & WAF 6.1.
> > > Our server has 1GB of RAM & is used only to run the cms 
> > > application.Problem is whenever we publish,unpublish & create new 
> > > articles in content-section there seems to be a memory leak & the 
> > > RAM usage increases upto 900 GB.After some time we get "out of 
> > > memory exception" and the application stops.Restarting of CMS also 
> > > doesn't help ,we have to reboot the system to get back the used 
> > > memory.Is this
> > 
> > > a bug in CMS or have we missed any configuration.
> > > Any help regarding this issue will be greatly appreciated.
> > > 
> > > Thanking in Advance,
> > > Sukesh Shetty
> > > 
> > 
> > --
> > Redhat-ccm-list mailing list
> > [email protected]
> > https://www.redhat.com/mailman/listinfo/redhat-ccm-list
> > Archives: https://www.redhat.com/pipermail/redhat-ccm-list/
> > 
> > 
> > 
> > 
> 
> --
> Redhat-ccm-list mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/redhat-ccm-list
> Archives: https://www.redhat.com/pipermail/redhat-ccm-list/
> 
> 
> 
> 

-- 
Redhat-ccm-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/redhat-ccm-list
Archives: https://www.redhat.com/pipermail/redhat-ccm-list/