DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15845>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15845 4.1.19 Memory Leak when creating compilier for JSP pages [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | ------- Additional Comments From [EMAIL PROTECTED] 2003-01-22 13:08 ------- Glenn, A map is used in the class org.apache.jasper.compiler.JspRuntimeContext the maps name is jsps and is declared as private Map jsps = Collections.synchronizedMap( new HashMap()); this map contains the uri off the jsp pages that are compiled as the key and the JspServletWrapper as the value. in turn the JspServletWrapper contains the JspCompilationContext which contains the Compiler and all the stuff that goes with it. this map continues to build up over time taking up huge amounts of memory if you have a lot of uncompiled jsp pages. the JspRuntimeContext.removeWrapper() method never gets called so this infomation is never garbage collected. I do not have a great understanding of what this code is trying to do so if you dont want to help me look into the problem if you could atleast help me understand what is suppose to be happening I will try and fix the leak myself. If you want to reproduce this bug just delete your jsp cache, turn on verbose:gc and then go to all your uncompiled jsp pages. you can watch the memory climb from there. thanks, John -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
