Hi, For the last few months, issues.apache.org/jira has been running out of memory about once a week. We've finally got it running in a profiler, and are seeing most of the memory (eg. 486 of 572Mb) used up by char[] buffers in BodyContentImpl. Here is a sample GC Root -> Object trace:
char[16777218] cb of org.apache.jasper.runtime.BodyContentImpl [0] of org.apache.jasper.runtime.BodyContentImpl[7] outs of org.apache.jasper.runtime.PageContextImpl [86] of java.lang.Object[101] pool of org.apache.jasper.util.SimplePool pool of org.apache.jasper.runtime.JspFactoryImpl deflt of javax.servlet.jsp.JspFactory [57] of java.lang.Object[641] elementData of java.util.Vector classes of org.apache.catalina.loader.StandardClassLoader [Other] There seems to be a constantly increasing number of BodyContentImpl objects in the system: 1 May: 93 Objects (126Mb) 2 May: 107 Objects (263Mb) 3 May: 492 Objects (486MB) (the first two were taken directly after a full gc) It appears to be a case of this bug: http://issues.apache.org/bugzilla/show_bug.cgi?id=37793 Perhaps this bug affects the ASF JIRA in particular (and not most people) because people occasionally request huge (20-30Mb) pages. There are 23 BodyContentImpls between 33Mb and 10Mb in the last dump, and due to the pooling, these all stick around taking up memory. Could anyone comment on this issue? Remy seemed to think it was 'as intended', and the bug is marked WONTFIX. I'm happy to provide yourkit memory dumps or access to the server if necessary. We're currently running 5.5.16. Thanks! Jeff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
