On 11/10/2010 17:30, Anurag Kapur wrote: > 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. > > https://issues.apache.org/bugzilla/show_bug.cgi?id=37793 > > 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?
I suspect it would only work if the app has JSPs which were pre-compiled against 5.5.9, rather than a newer version. p
0x62590808.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
