source: nutchez-0.1/tomcat/webapps/docs/RELEASE-NOTES.txt @ 141

Last change on this file since 141 was 66, checked in by waue, 16 years ago

NutchEz - an easy way to nutch

File size: 7.1 KB
Line 
1================================================================================
2  Licensed to the Apache Software Foundation (ASF) under one or more
3  contributor license agreements.  See the NOTICE file distributed with
4  this work for additional information regarding copyright ownership.
5  The ASF licenses this file to You under the Apache License, Version 2.0
6  (the "License"); you may not use this file except in compliance with
7  the License.  You may obtain a copy of the License at
8
9      http://www.apache.org/licenses/LICENSE-2.0
10
11  Unless required by applicable law or agreed to in writing, software
12  distributed under the License is distributed on an "AS IS" BASIS,
13  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
14  See the License for the specific language governing permissions and
15  limitations under the License.
16================================================================================
17
18$Id: RELEASE-NOTES 612940 2008-01-17 19:22:26Z markt $
19
20
21                     Apache Tomcat Version 6.0.18
22                            Release Notes
23
24
25=============================
26KNOWN ISSUES IN THIS RELEASE:
27=============================
28
29* Dependency Changes
30* JNI Based Applications
31* Bundled APIs
32* Web application reloading and static fields in shared libraries
33* Tomcat on Linux
34* Enabling SSI and CGI Support
35* Security manager URLs
36* Symlinking static resources
37* Enabling invoker servlet
38* Viewing the Tomcat Change Log
39* When all else fails
40
41
42===================
43Dependency Changes:
44===================
45Tomcat 6.0 is designed to run on JSE 5.0 and later.
46
47In addition, Tomcat 6.0 uses the Eclipse JDT Java compiler for compiling
48JSP pages.  This means you no longer need to have the complete
49Java Development Kit (JDK) to run Tomcat, but a Java Runtime Environment
50(JRE) is sufficient.  The Eclipse JDT Java compiler is bundled with the
51binary Tomcat distributions.  Tomcat can also be configured to use the
52compiler from the JDK to compile JSPs, or any other Java compiler supported
53by Apache Ant.
54
55
56=======================
57JNI Based Applications:
58=======================
59Applications that require native libraries must ensure that the libraries have
60been loaded prior to use.  Typically, this is done with a call like:
61
62  static {
63    System.loadLibrary("path-to-library-file");
64  }
65
66in some class.  However, the application must also ensure that the library is
67not loaded more than once.  If the above code were placed in a class inside
68the web application (i.e. under /WEB-INF/classes or /WEB-INF/lib), and the
69application were reloaded, the loadLibrary() call would be attempted a second
70time.
71
72To avoid this problem, place classes that load native libraries outside of the
73web application, and ensure that the loadLibrary() call is executed only once
74during the lifetime of a particular JVM.
75
76
77=============
78Bundled APIs:
79=============
80A standard installation of Tomcat 6.0 makes all of the following APIs available
81for use by web applications (by placing them in "lib"):
82* annotations-api.jar (Annotations package)
83* catalina.jar (Tomcat Catalina implementation)
84* catalina-ant.jar (Tomcat Catalina Ant tasks)
85* catalina-ha.jar (High availability package)
86* catalina-tribes.jar (Group communication)
87* el-api.jar (EL 2.1 API)
88* jasper.jar (Jasper 2 Compiler and Runtime)
89* jasper-el.jar (Jasper 2 EL implementation)
90* jasper-jdt.jar (Eclipse JDT 3.3 Java compiler)
91* jsp-api.jar (JSP 2.1 API)
92* servlet-api.jar (Servlet 2.5 API)
93* tomcat-coyote.jar (Tomcat connectors and utility classes)
94* tomcat-dbcp.jar (package renamed database connection pool based on Commons DBCP)
95
96You can make additional APIs available to all of your web applications by
97putting unpacked classes into a "classes" directory (not created by default),
98or by placing them in JAR files in the "lib" directory.
99
100To override the XML parser implementation or interfaces, use the endorsed
101mechanism of the JVM. The default configuration defines JARs located in
102"endorsed" as endorsed.
103
104
105================================================================
106Web application reloading and static fields in shared libraries:
107================================================================
108Some shared libraries (many are part of the JDK) keep references to objects
109instantiated by the web application. To avoid class loading related problems
110(ClassCastExceptions, messages indicating that the classloader
111is stopped, etc.), the shared libraries state should be reinitialized.
112
113Something which might help is to avoid putting classes which would be
114referenced by a shared static field in the web application classloader,
115and putting them in the shared classloader instead (JARs should be put in the
116"lib" folder, and classes should be put in the "classes" folder).
117
118
119================
120Tomcat on Linux:
121================
122GLIBC 2.2 / Linux 2.4 users should define an environment variable:
123export LD_ASSUME_KERNEL=2.2.5
124
125Redhat Linux 9.0 users should use the following setting to avoid
126stability problems:
127export LD_ASSUME_KERNEL=2.4.1
128
129There are some Linux bugs reported against the NIO sendfile behavior, make sure you
130have a JDK that is up to date, or disable sendfile behavior in the Connector.<br/>
1316427312: (fc) FileChannel.transferTo() throws IOException "system call interrupted"<br/>
1325103988: (fc) FileChannel.transferTo should return -1 for EAGAIN instead throws IOException<br/>
1336253145: (fc) FileChannel.transferTo on Linux fails when going beyond 2GB boundary<br/>
1346470086: (fc) FileChannel.transferTo(2147483647, 1, channel) cause "Value too large" exception<br/>
135
136
137=============================
138Enabling SSI and CGI Support:
139=============================
140Because of the security risks associated with CGI and SSI available
141to web applications, these features are disabled by default. 
142
143To enable and configure CGI support, please see the cgi-howto.html page.
144
145To enable and configue SSI support, please see the ssi-howto.html page.
146
147
148======================
149Security manager URLs:
150======================
151In order to grant security permissions to JARs located inside the
152web application repository, use URLs of of the following format
153in your policy file:
154
155file:${catalina.home}/webapps/examples/WEB-INF/lib/driver.jar
156
157
158============================
159Symlinking static resources:
160============================
161By default, Unix symlinks will not work when used in a web application to link
162resources located outside the web application root directory.
163
164This behavior is optional, and the "allowLinking" flag may be used to disable
165the check.
166
167
168=========================
169Enabling invoker servlet:
170=========================
171Starting with Tomcat 4.1.12, the invoker servlet is no longer available by
172default in all webapps. Enabling it for all webapps is possible by editing
173$CATALINA_HOME/conf/web.xml to uncomment the "/servlet/*" servlet-mapping
174definition.
175
176Using the invoker servlet in a production environment is not recommended and
177is unsupported.  More details are available on the Tomcat FAQ at
178http://tomcat.apache.org/faq/misc.html#invoker.
179
180
181==============================
182Viewing the Tomcat Change Log:
183==============================
184See changelog.html in this directory.
185
186
187====================
188When all else fails:
189====================
190See the FAQ
191http://tomcat.apache.org/faq/
Note: See TracBrowser for help on using the repository browser.