yoavs 2004/09/09 09:56:59 Modified: . RELEASE-NOTES Log: Took out stale and irrelevant section (for Tomcat 5.5, still relevant for 5.0 and prior releases) about javac leaking memory. Revision Changes Path 1.24 +1 -15 jakarta-tomcat-5/RELEASE-NOTES Index: RELEASE-NOTES =================================================================== RCS file: /home/cvs/jakarta-tomcat-5/RELEASE-NOTES,v retrieving revision 1.23 retrieving revision 1.24 diff -u -r1.23 -r1.24 --- RELEASE-NOTES 30 Aug 2004 21:32:04 -0000 1.23 +++ RELEASE-NOTES 9 Sep 2004 16:56:59 -0000 1.24 @@ -15,7 +15,6 @@ * JNI Based Applications * Bundled APIs * Web application reloading and static fields in shared libraries -* JAVAC leaking memory * Tomcat on Linux * Enabling SSI and CGI Support * Security manager URLs @@ -106,19 +105,6 @@ referenced by a shared static field in the web application classloader, and putting them in the shared classloader instead (JARs should be put in the "lib" folder, and classes should be put in the "classes" folder). - - -===================== -JAVAC leaking memory: -===================== -The Java compiler leaks memory each time a class is compiled. Web applications -containing hundreds of JSP files may as a result trigger out of memory errors -once a significant number of pages have been accessed. The memory can only be -freed by stopping Tomcat and then restarting it. - -The JSP command line compiler (JSPC) can also be used to precompile the JSPs. - -Note: This issue has been fixed in Sun JDK 1.4.x. ================
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
