Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
From: "Vadim Gritsenko" <vadim.gritsenko@verizon.net>
To: <cocoon-dev@xml.apache.org>
Subject: RE: C2 Bug Locating Tips
Date: Thu, 14 Mar 2002 11:34:48 -0500
Message-ID: <002001c1cb76$28663190$90a4558b@vgritsenkopc>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-Reply-To: <A0DE1DAA-3765-11D6-AA1B-0030654777A6@adolos.co.uk>
Importance: Normal

> From: Stuart Roebuck [mailto:stuart.roebuck@adolos.co.uk]
> 
>              +---------------------------------------------+
>              |  LOOKING FOR TIPS ON HOW TO DEBUG COCOON ?  |
>              +---------------------------------------------+
> 
> unfortunately, I don't have a great deal of my own, but I'm happy to
> compile other peoples into something useful if anyone would like to
> contribute some suggestions on how I might track down an apparent
memory
> leak in the recent CVS versions of Cocoon!
> 
> Seeing as there is talk of... *A NEW RELEASE*...I thought it was time
I
> did some work on ironing this problem out now.
> 
> My setup is:
> 		Cocoon 2 (latest CVS) - but problems have occurred for a
month
> or so now.
> 		Tomcat 4.0.1
> 		Mac OS X 10.1.3 (latest Java release) - but problems
occurred
> before it.
> 
> After a modest amount of Cocoon action, I get an OutOfMemoryError in
the
> Tomcat localhost_log (see below) and to be completely honest, I
haven't
> much of a clue how I'm going to track down the associated memory leak.
> 
> 	(  which reminds me - how do you stop debug level messages    )
>      (  appearing in the Tomcat localhost_log file?  Changing all  )
>      (  the references to "DEBUG" in logkit.conf turns off DEBUG   )
>      (  level output in the WEB-INF/logs directory, but not in     )
>      (  the Tomcat log directory.                                  )
> 
> I'm now using the Pizza compiler, so the associated Javac memory leak
> shouldn't be there.
> 
> I've reduced the store-janitor heapsize value from the default
67108864
> to 60000000 running from a default Mac OS X Java configuration of 64Mb
> max heap and this appears to delay the onset of problems.
> 
> The problems weren't present in the past, and we currently have a
> pre-release site <http://www.cueandreview.co.uk/> running on an older
> Cocoon 2 release which doesn't exhibit this behaviour.  It's running
off
> a FreeBSD based machine, but it was developed without problems on Mac
OS
> X (with the release of Cocoon it is running on on FreeBSD).
> 
> So I'm inclined to think that the problem is something that has been
> introduced in Cocoon, rather than anything platform specific or
> sitemap / processing specific - but I could be wrong.

Still, for anyone to debug your leak, one has to know what components
you are using. Some components could have memory leak, while others do
not. So, /please provide list of used components/ :)


> Significant things that have changed (and are being used) between the
> reliable version and the current include:
> 	Xerces 1.4.4 --> Xerces 2.0.x
> 	TreeProcessor
> 	JispStore
> 	Pizza compiler
> 
> This may or may not be connected with:
> 
> 	<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6868>

I fail to see connection...

> Any thoughts, hints, suggestions?

*Memory leak debugging how-to:*

1. Download trial of OptimizeIt
2. Decrease pool sizes to the minimum
3. Launch Tomcat/Cocoon
4. Exercise app for a while
5. Run gc several times (button on OptimizeIt's toolbar)
6. Click on "mark"
7. Access one URL once
8. Repeat 5
9. Sort by object count difference
10. View allocation backtraces of the objects which count increased.
11. Repeat 5-10 for all URLs.

If everywhere you see +0 - no memory leaks found.

Vadim


> Stuart.

<snip/>


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org