You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by ma...@apache.org on 2021/11/02 14:19:57 UTC
svn commit: r1894684 - in /tomcat/site/trunk: docs/migration-10.html
docs/migration-85.html docs/migration-9.html docs/migration.html
xdocs/migration-10.xml xdocs/migration-85.xml xdocs/migration-9.xml
xdocs/migration.xml
Author: markt
Date: Tue Nov 2 14:19:57 2021
New Revision: 1894684
URL: http://svn.apache.org/viewvc?rev=1894684&view=rev
Log:
Add note on impact of Commons FileUpload changes on direct memory usage
Modified:
tomcat/site/trunk/docs/migration-10.html
tomcat/site/trunk/docs/migration-85.html
tomcat/site/trunk/docs/migration-9.html
tomcat/site/trunk/docs/migration.html
tomcat/site/trunk/xdocs/migration-10.xml
tomcat/site/trunk/xdocs/migration-85.xml
tomcat/site/trunk/xdocs/migration-9.xml
tomcat/site/trunk/xdocs/migration.xml
Modified: tomcat/site/trunk/docs/migration-10.html
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/migration-10.html?rev=1894684&r1=1894683&r2=1894684&view=diff
==============================================================================
--- tomcat/site/trunk/docs/migration-10.html (original)
+++ tomcat/site/trunk/docs/migration-10.html Tue Nov 2 14:19:57 2021
@@ -161,6 +161,12 @@ of Apache Tomcat.</p>
checks are complete. If the application is marked as serviced when the
method is called, the method will be a NO-OP.</p>
</li>
+ <li><p>In 10.0.11 onwards, as a result of the updated fork of Commons
+ FileUpload now using <code>java.nio.file.Files</code>, applications
+ using multi-part uploads need to ensure that the JVM is configured with
+ sufficient direct memory to store all in progress multi-part
+ uploads.</p>
+ </li>
</ul>
</div></div>
Modified: tomcat/site/trunk/docs/migration-85.html
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/migration-85.html?rev=1894684&r1=1894683&r2=1894684&view=diff
==============================================================================
--- tomcat/site/trunk/docs/migration-85.html (original)
+++ tomcat/site/trunk/docs/migration-85.html Tue Nov 2 14:19:57 2021
@@ -245,6 +245,7 @@ of Apache Tomcat.</p>
blocked with a 403.</p>
<p>Reference: <a href="tomcat-8.5-doc/config/ajp.html">AJP
connector</a>.</p>
+ </li>
<li><p>In 8.5.64 onwards, the semantics of the
<code>HostConfig.check(String)</code> method have changed. Rather than
marking the application as serviced before calling the method, the
@@ -253,6 +254,11 @@ of Apache Tomcat.</p>
checks are complete. If the application is marked as serviced when the
method is called, the method will be a NO-OP.</p>
</li>
+ <li><p>In 8.5.71 onwards, as a result of the updated fork of Commons
+ FileUpload now using <code>java.nio.file.Files</code>, applications
+ using multi-part uploads need to ensure that the JVM is configured with
+ sufficient direct memory to store all in progress multi-part
+ uploads.</p>
</li>
</ul>
</div></div>
Modified: tomcat/site/trunk/docs/migration-9.html
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/migration-9.html?rev=1894684&r1=1894683&r2=1894684&view=diff
==============================================================================
--- tomcat/site/trunk/docs/migration-9.html (original)
+++ tomcat/site/trunk/docs/migration-9.html Tue Nov 2 14:19:57 2021
@@ -334,6 +334,12 @@ of Apache Tomcat.</p>
cause a startup error if they are present in the configuration, but
may produce a warning and will have no effect.</p>
</li>
+ <li><p>In 9.0.53 onwards, as a result of the updated fork of Commons
+ FileUpload now using <code>java.nio.file.Files</code>, applications
+ using multi-part uploads need to ensure that the JVM is configured with
+ sufficient direct memory to store all in progress multi-part
+ uploads.</p>
+ </li>
</ul>
</div></div>
Modified: tomcat/site/trunk/docs/migration.html
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/migration.html?rev=1894684&r1=1894683&r2=1894684&view=diff
==============================================================================
--- tomcat/site/trunk/docs/migration.html (original)
+++ tomcat/site/trunk/docs/migration.html Tue Nov 2 14:19:57 2021
@@ -7,18 +7,18 @@
sure that the JVM that is installed on your system supports at least the
required Java version. While it is possible that older versions of Tomcat may
not be compatible with newer JVMs, all the currently supported Apache Tomcat
-versions (7.0.x, 8.5.x, 9.0.x and 10.0.x) are known to run correctly on Java 8
+versions (8.5.x, 9.0.x, 10.0.x and 10.1.x) are known to run correctly on Java 8
JVMs.</p>
-<p>When migrating from one major Tomcat version to another (e.g. from Tomcat 7
-to Tomcat 8, or from Tomcat 8 to Tomcat 8.5),
+<p>When migrating from one major Tomcat version to another (e.g. from Tomcat 8
+to Tomcat 9, or from Tomcat 9 to Tomcat 10),
you should not copy the configuration files from the old version
to the new version. The recommended approach is to start with the default
configuration of the new version of Apache Tomcat and to adjust it as necessary.
</p>
<p>When migrating from one minor release to another minor release within the
-same major release (e.g. from Tomcat 7.0.27 to Tomcat 7.0.28) you can retain the
+same major release (e.g. from Tomcat 9.0.29 to Tomcat 9.0.30) you can retain the
configuration files, but you should check to see if any defaults have changed
and/or if any new elements have been added and adjust your configuration files
accordingly.</p>
Modified: tomcat/site/trunk/xdocs/migration-10.xml
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/migration-10.xml?rev=1894684&r1=1894683&r2=1894684&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs/migration-10.xml (original)
+++ tomcat/site/trunk/xdocs/migration-10.xml Tue Nov 2 14:19:57 2021
@@ -174,6 +174,12 @@ of Apache Tomcat.</p>
checks are complete. If the application is marked as serviced when the
method is called, the method will be a NO-OP.</p>
</li>
+ <li><p>In 10.0.11 onwards, as a result of the updated fork of Commons
+ FileUpload now using <code>java.nio.file.Files</code>, applications
+ using multi-part uploads need to ensure that the JVM is configured with
+ sufficient direct memory to store all in progress multi-part
+ uploads.</p>
+ </li>
</ul>
</subsection>
Modified: tomcat/site/trunk/xdocs/migration-85.xml
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/migration-85.xml?rev=1894684&r1=1894683&r2=1894684&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs/migration-85.xml (original)
+++ tomcat/site/trunk/xdocs/migration-85.xml Tue Nov 2 14:19:57 2021
@@ -258,6 +258,7 @@ of Apache Tomcat.</p>
blocked with a 403.</p>
<p>Reference: <a href="tomcat-8.5-doc/config/ajp.html">AJP
connector</a>.</p>
+ </li>
<li><p>In 8.5.64 onwards, the semantics of the
<code>HostConfig.check(String)</code> method have changed. Rather than
marking the application as serviced before calling the method, the
@@ -266,6 +267,11 @@ of Apache Tomcat.</p>
checks are complete. If the application is marked as serviced when the
method is called, the method will be a NO-OP.</p>
</li>
+ <li><p>In 8.5.71 onwards, as a result of the updated fork of Commons
+ FileUpload now using <code>java.nio.file.Files</code>, applications
+ using multi-part uploads need to ensure that the JVM is configured with
+ sufficient direct memory to store all in progress multi-part
+ uploads.</p>
</li>
</ul>
</subsection>
Modified: tomcat/site/trunk/xdocs/migration-9.xml
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/migration-9.xml?rev=1894684&r1=1894683&r2=1894684&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs/migration-9.xml (original)
+++ tomcat/site/trunk/xdocs/migration-9.xml Tue Nov 2 14:19:57 2021
@@ -347,6 +347,12 @@ of Apache Tomcat.</p>
cause a startup error if they are present in the configuration, but
may produce a warning and will have no effect.</p>
</li>
+ <li><p>In 9.0.53 onwards, as a result of the updated fork of Commons
+ FileUpload now using <code>java.nio.file.Files</code>, applications
+ using multi-part uploads need to ensure that the JVM is configured with
+ sufficient direct memory to store all in progress multi-part
+ uploads.</p>
+ </li>
</ul>
</subsection>
Modified: tomcat/site/trunk/xdocs/migration.xml
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/migration.xml?rev=1894684&r1=1894683&r2=1894684&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs/migration.xml (original)
+++ tomcat/site/trunk/xdocs/migration.xml Tue Nov 2 14:19:57 2021
@@ -14,18 +14,18 @@
sure that the JVM that is installed on your system supports at least the
required Java version. While it is possible that older versions of Tomcat may
not be compatible with newer JVMs, all the currently supported Apache Tomcat
-versions (7.0.x, 8.5.x, 9.0.x and 10.0.x) are known to run correctly on Java 8
+versions (8.5.x, 9.0.x, 10.0.x and 10.1.x) are known to run correctly on Java 8
JVMs.</p>
-<p>When migrating from one major Tomcat version to another (e.g. from Tomcat 7
-to Tomcat 8, or from Tomcat 8 to Tomcat 8.5),
+<p>When migrating from one major Tomcat version to another (e.g. from Tomcat 8
+to Tomcat 9, or from Tomcat 9 to Tomcat 10),
you should not copy the configuration files from the old version
to the new version. The recommended approach is to start with the default
configuration of the new version of Apache Tomcat and to adjust it as necessary.
</p>
<p>When migrating from one minor release to another minor release within the
-same major release (e.g. from Tomcat 7.0.27 to Tomcat 7.0.28) you can retain the
+same major release (e.g. from Tomcat 9.0.29 to Tomcat 9.0.30) you can retain the
configuration files, but you should check to see if any defaults have changed
and/or if any new elements have been added and adjust your configuration files
accordingly.</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org