tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: Tomcat 5.5.25 | Memory leak in Web Application
Date Tue, 12 Oct 2010 18:45:06 GMT
Hash: SHA1


On 10/11/2010 12:30 PM, Anurag Kapur wrote:
> I have added my problem statement with Images to by blog here:

The memory profile you show there appears to have a good GC curve:
tenured generation stabilizes over time, and eden space sees regular
activity that is eventually collected. The process repeats itself as GCs
take place.

I see no problem, here, other than your OOME. I disagree with your
analysis that this heap utilization graph "suggests a memory leak type

> The objects holding references to the character arrays that ultimately
> consume all the memory are of type
> org.apache.jasper.runtime.BodyContentImpl as indicated in the object
> reference tree below:
> There was a bug reported in Tomcat 5.5.9 which says
> The problem is that this huge array never gets reset due to the object pooling
> implementation in Jasper (JspFactoryImpl maintains a pool of PageContextImpl
> objects. Each PageContextImpl object maintains an array of BodyContentImpl
> objects), so the memory it consumed is never returned to the heap.
> We do not use the suggest JVM argument in our Tomcat 5.5.27 JVM
> -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
> Could adding this argument to the Tomcat JVM resolve the problem?

Certainly you could try it. It appears from this bug report that this
should only be a problem with JSPs where there are large body tags. Are
you using such body tags? If so, then this may help. Otherwise, it
probably will not help.

markt marked this bug as FIXED, but I see no indication of a resolution.
Perhaps that was meant to be WONTFIX?

- -chris
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla -


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message