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|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2003-01-22 15:54 ------- The Compiler is needed to check for JSP pages which are out of date and need to be recompiled. But you do have a valid point that there are some objects with references to them being maintained by the Compiler class between JSP page compiles that are not needed and could increase memory usage. I found the following in the Compiler class which are only used during a compile and could be dereferenced once the compile is complete. Setting these to null after a compile could reduce the memory footprint on a production server where JSP recompiles happen infrequently. private ErrorDispatcher errDispatcher private PageInfo pageInfo; private JasperAntLogger logger; protected Project project=null; protected Node.Nodes pageNodes; Thanks for being persistant in pursuing this issue. Unless there is objection, I will make the necessary changes to the Compiler class. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
