I have a page that renders a very large report using the apache jstl tags. When the page has finished running, my memory usage jumps up 70MB. Even if I force a full garbage collection (verified in my garbage collector log), memory usage does not decrease. There is no data being cached or stored in the user's session, it's simply dumped into the request and rendered by the JSP. I've found that if I un-deploy the war and force a full garbage collection, memory usage drops 70MB. I've also found that after waiting about 30 minutes, the memory is released.
When I did memory snapshots before and after running that page, I could still see the page exists in memory (org.apache.jsp.ContactReport_jsp) and appears to be holding on to that 70MB. From what I've read (http://issues.apache.org/bugzilla/show_bug.cgi?id=25623) , it's seems like the memory that is used by the jstl foreach tag is not released until the page is destroyed. I'd like to verify this is truly the case and I'd also like to find out exactly what triggers the call to jspDestroy. Is there a timer, a thread, a memory threshold? Is there something I can/should configure to keep the page from eating up all of that memory for so long? I've tried disabling tag pooling, but that had no effect. Thanks!! ________________________________________________________________________ _____________ Bob Damato Cox Target Media Internet Technology Manager Largo, Florida Our greatest glory is not in never falling, but in rising every time we fall. -- Confucius
