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 44383] - Possible leak: tomcat does not release Jasper compilation contexts
Date Sun, 10 Feb 2008 21:38:29 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=44383>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=44383





------- Additional Comments From diosnoes@hotmail.com  2008-02-10 13:38 -------
I think I understand the issue now. If the JspServlet (Jasper) is in development
mode (the default) the compiler (JDTCompiler) keeps the Node information of the
page after the compilation to provide the source line in case of an error.

On our production server, this mode of operation more than doubles the needed
memory to run the applications.

I think this should be clarified in the documentation as it only relates the
option "development" to the behaviour with respect to modifications and not to
the extra memory cost of this information.

Thanks Mark for your response.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message