tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 15845] New: - Memory Leak when compiling JSP
Date Tue, 07 Jan 2003 16:11:12 GMT
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

Memory Leak when compiling JSP

           Summary: Memory Leak when compiling JSP
           Product: Tomcat 4
           Version: 4.1.14
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Jasper 2
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: jakarta@trollingers.com


when accessing lots of uncompiled jsp pages Jasper leaks memory.

I have found a temporary solution but am sure it is not good.

if you always force the JspCompilationContext to use a new Compiler when 
getCompiler() is called the leak goes away.  

When profiling Jasper the problem was that the JspCompilationContext, 
JspServletWrapper, JspRuntimeContext, and the Compiler never got gced because 
they where never dereferenced.  by forcing a new compiler each time it seems to 
solve this problem but not sure what others it could cause.

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message