tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: jakarta-tomcat-4.0 RELEASE-NOTES-4.1.txt RELEASE-PLAN-4.1.txt
Date Tue, 30 Apr 2002 08:41:46 GMT
remm        02/04/30 01:41:46

  Modified:    .        RELEASE-PLAN-4.1.txt
  Added:       .        RELEASE-NOTES-4.1.txt
  - Change my mind again and use a common release notes document.
  - Update status.
  Revision  Changes    Path
  1.8       +1 -2      jakarta-tomcat-4.0/RELEASE-PLAN-4.1.txt
  Index: RELEASE-PLAN-4.1.txt
  RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-PLAN-4.1.txt,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- RELEASE-PLAN-4.1.txt	25 Apr 2002 22:00:19 -0000	1.7
  +++ RELEASE-PLAN-4.1.txt	30 Apr 2002 08:41:46 -0000	1.8
  @@ -1,4 +1,4 @@
  -$Id: RELEASE-PLAN-4.1.txt,v 1.7 2002/04/25 22:00:19 remm Exp $
  +$Id: RELEASE-PLAN-4.1.txt,v 1.8 2002/04/30 08:41:46 remm Exp $
                         Release Plan for Apache Tomcat 4.1
  @@ -125,7 +125,6 @@
   7160 Jasper compiles files to same classname
   7993 parameters in <jsp:plugin> for jsp Document do not work
   8005 Bad Param passing with jsp:include
  -8290 Problem in the code generated by jasper 2
   Unconfirmed Bugs (Awaiting Reproducible Failure Case):
  1.1                  jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt
  Index: RELEASE-NOTES-4.1.txt
                        Apache Tomcat Version 4.1
                              Release Notes
  $Id: RELEASE-NOTES-4.1.txt,v 1.1 2002/04/30 08:41:46 remm Exp $
  This document describes the changes that have been made in the current
  development version of Apache Tomcat, relative to the Tomcat 4.0 release.
  The release notes for all prior releases of Tomcat 4.0 are also included, for
  your reference.
  Bug reports should be entered at the bug reporting system for
  Jakarta projects at:

  Please report bugs and feature requests under product name "Tomcat 4".
  General New Features:
  Catalina New Features:
  Jasper New Features:
  [4.1.1] JspServlet, Options:
          Add new "reloading" flag allowing to disable the JSP reloading checks,
          to allow better performance on production servers.
  Generic Bug Fixes:
  Catalina Bug Fixes:
  [4.1.1] #8611
          Summary: Sealed .jar files in WEB-INF/lib always fail to load 
                   second class
          The classloader will now generate codebases URL for classes loaded from
          JAR file which point to the JAR, intead of using a nested jar: URL.
          This change will affect security manager policy files.
  Jasper Bug Fixes:
  [4.1.1] #8290
          Summary: Problem in the code generated by jasper 2
          This workaround for a JDK bug (BugParade Id: 4414162) introduces 
          a massive performance improvement when using pages containing 
          lots of tags.
  * Tomcat 4.0 and JNI Based Applications
  * Tomcat 4.0 Standard APIs Available
  * Tomcat 4.0 and XML Parsers
  * Web application reloading and static fields in shared libraries
  * JAVAC leaking memory
  * Linux and Sun JDK 1.2.x - 1.3.x
  * Jasper and Jikes
  * Enabling SSI and CGI Support
  * Tomcat examples web application
  Tomcat 4.0 and JNI Based Applications:
  Applications that require native libraries must ensure that the libraries have
  been loaded prior to use.  Typically, this is done with a call like:
    static {
  in some class.  However, the application must also ensure that the library is
  not loaded more than once.  If the above code were placed in a class inside
  the web application (i.e. under /WEB-INF/classes or /WEB-INF/lib), and the
  application were reloaded, the loadLibrary() call would be attempted a second
  To avoid this problem, place classes that load native libraries outside of the
  web application, and ensure that the loadLibrary() call is executed only once
  during the lifetime of a particular JVM.
  Tomcat 4.0 Standard APIs Available:
  A standard installation of Tomcat 4 makes all of the following APIs available
  for use by web applications (by placing them in "common/lib" or "shared/lib"):
  * activation.jar (Java Activation Framework)
  * commons-collections.jar (Commons Collections 2.0)
  * commons-dbcp.jar (Commons DBCP)
  * commons-logging.jar (Commons Logging 1.0)
  * commons-pool.jar (Commons Pool)
  * jasper-compiler.jar (Jasper 2 Compiler)
  * jasper-runtime.jar (Jasper 2 Runtime)
  * jdbc2_0-stdext.jar (JDBC 2.0 Optional Package, javax.sql.*)
  * jndi.jar (JNDI 1.2 base API classes)
  * jta-spec1_0_1 (Java Transacation API 1.0.1)
  * mail.jar (JavaMail 1.2)
  * naming-common.jar (JNDI Context implementation)
  * naming-factory.jar (JNDI object factories)
  * naming-resources.jar (JNDI DirContext implementations)
  * servlet.jar (Servlet 2.3 and JSP 1.2 APIs)
  * xercesImpl.jar (Xerces 2.0.1; located in "common/endorsed")
  * xmlParserAPIs.jar (DOM 2 and SAX 2 APIs; located in "common/endorsed")
  You can make additional APIs available to all of your web applications by
  putting unpacked classes into a "classes" directory (not created by default),
  or by placing them in JAR files in the "lib" directory.
  Tomcat 4.0 and XML Parsers:
  As described above, Tomcat 4.0 makes an XML parser (and many other standard
  APIs) available to web applications.  This parser is also used internally
  to parse web.xml files and the server.xml configuration file.  If you wish,
  you may replace the "xercesImpl.jar" file in "common/endorsed" with another 
  XML parser, as long as it is compatible with the JAXP/1.1 APIs.
  Web application reloading and static fields in shared libraries:
  Some shared libraries (many are part of the JDK) keep references to objects
  instantiated by the web application. To avoid class loading related problems
  (ClassCastExceptions, messages indicating that the classloader 
  is stopped, ...), the shared libraries state should be reinitialized.
  Something which could help is to avoid putting classes which would be 
  referenced by a shared static field in the web application classloader, 
  and put them in the shared classloader instead (the 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.
  Linux and Sun JDK 1.2.x - 1.3.x:
  Virtual machine crashes can be experienced when using certain combinations of
  kernel / glibc under Linux with Sun Hotspot 1.2 to 1.3. The crashes were 
  reported to occur mostly on startup. Sun JDK 1.4 does not exhibit the problems,
  and neither does IBM JDK for Linux.
  The problems can be fixed by reducing the default stack size. At bash shell, 
  do "ulimit -s 2048"; use "limit stacksize 2048" for tcsh.
  GLIBC 2.2 / Linux 2.4 users should also define an environment variable:
  export LD_ASSUME_KERNEL=2.2.5
  Tomcat 4.0 and Sun JDK 1.4 beta 3:
  Some unpredictable classloading behavior has been reported when Tomcat is 
  used with Sun JDK 1.4 beta 3. The problem has been fixed with Sun JDK 1.4 
  Realease Candidate or later.
  Jasper and Jikes:
  Jikes can be used with the Jasper JSP page compiler, but the runtime classes 
  JAR of the JDK or JRE (depending on what is installed on the computer) must
  be added to the system classpath.
  This can be achieved by editing the main catalina script, and adding the rt.jar
  On Windows:
    line 71 of %CATALINA_HOME%\bin\catalina.bat, change
  set CP=%CATALINA_HOME%\bin\bootstrap.jar;%JAVA_HOME%\lib\tools.jar
  set CP=%JAVA_HOME%\jre\lib\rt.jar;%CATALINA_HOME%\bin\bootstrap.jar;%JAVA_HOME%\lib\tools.jar
  On Unix or Unix-like OSes:
    line 89 of $CATALINA_HOME/bin/, change
  Enabling SSI and CGI Support:
  Having CGI and SSI available to web applications created security problems when
  using a security manager (as a malicious web application could use them to 
  sidestep the security manager access control). In Tomcat 4.0, they have been
  disabled by default, as our goal is to provide a fully secure default 
  configuration. However, CGI and SSI remain available.
  On Windows:
  * rename the file %CATALINA_HOME%\server\lib\servlets-cgi.renametojar to
  * rename the file %CATALINA_HOME%\server\lib\servlets-ssi.renametojar to
  * in %CATALINA_HOME%\conf\web.xml, uncomment the servlet declarations starting
    line 165 and 213, as well as the associated servlet mappings 
    line 265 and 274. Alternately, these servlet declarations and mappings can
    be added to your web application deployment descriptor.
  On Unix:
  * rename the file $CATALINA_HOME/server/lib/servlets-cgi.renametojar to
  * rename the file $CATALINA_HOME/server/lib/servlets-ssi.renametojar to
  * in $CATALINA_HOME/conf/web.xml, uncomment the servlet declarations starting
    line 165 and 213, as well as the associated servlet mappings 
    line 265 and 274. Alternately, these servlet declarations and mappings can
    be added to your web application deployment descriptor.
  Tomcat examples web application:
  It is recommended to remove the "examples" web application when deploying
  Tomcat on a production server.

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message