Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 88790 invoked from network); 10 Feb 2008 21:39:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Feb 2008 21:39:00 -0000 Received: (qmail 12617 invoked by uid 500); 10 Feb 2008 21:38:46 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 12554 invoked by uid 500); 10 Feb 2008 21:38:46 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 12543 invoked by uid 500); 10 Feb 2008 21:38:46 -0000 Delivered-To: apmail-jakarta-tomcat-dev@jakarta.apache.org Received: (qmail 12540 invoked by uid 99); 10 Feb 2008 21:38:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Feb 2008 13:38:46 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Feb 2008 21:38:10 +0000 Received: by brutus.apache.org (Postfix, from userid 33) id 4C8DC71406C; Sun, 10 Feb 2008 13:38:29 -0800 (PST) From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Subject: DO NOT REPLY [Bug 44383] - Possible leak: tomcat does not release Jasper compilation contexts In-Reply-To: X-Bugzilla-Reason: AssignedTo Message-Id: <20080210213830.4C8DC71406C@brutus.apache.org> Date: Sun, 10 Feb 2008 13:38:29 -0800 (PST) X-Virus-Checked: Checked by ClamAV on apache.org DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . 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