November releases
Hi all, There doesn't seem to be much in the changelogs at the moment and the code signing is currently unavailable as the renewal process is taking longer than expected. Therefore, my current thinking is to delay the release process and review the situation towards the end of the week. Thoughts? Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 65350] The index ID of the request header that Jetty sent to Tomcat was not found in the index table on the Tomcat side
https://bz.apache.org/bugzilla/show_bug.cgi?id=65350 Mark Thomas changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME --- Comment #8 from Mark Thomas --- Several further months have passed with no further information provided. I am therefore resolving this as WORKSFORME. If, and only if, you are able to provide a test case that demonstrates this issue, feel free to re-open this issue and provide the test case. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 65408] tomcat8.5.X occurs an AssertionError occationally after running for a period of time
https://bz.apache.org/bugzilla/show_bug.cgi?id=65408 Mark Thomas changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME --- Comment #14 from Mark Thomas --- Several further months have passed with no further information provided. I am therefore resolving this as WORKSFORME. If, and only if, you are able to provide a test case that demonstrates this issue, feel free to re-open this issue and provide the test case. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 65455] after about 10 days ago, tomcat8.5.63 can't response web request again
https://bz.apache.org/bugzilla/show_bug.cgi?id=65455 Mark Thomas changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEEDINFO|RESOLVED --- Comment #6 from Mark Thomas --- Several further months have passed with no further information provided. I am therefore resolving this as WORKSFORME. If, and only if, you are able to provide a test case that demonstrates this issue, feel free to re-open this issue and provide the test case. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[tomcat] branch 10.0.x updated: Fix back-port of previous commit
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch 10.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/10.0.x by this push:
new cb6e698 Fix back-port of previous commit
cb6e698 is described below
commit cb6e69855cdf4b8951c0a25288114350977ef90f
Author: Mark Thomas
AuthorDate: Tue Nov 2 12:03:39 2021 +
Fix back-port of previous commit
---
java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java
b/java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java
index 12bf11e..5163623 100644
--- a/java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java
+++ b/java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java
@@ -32,8 +32,8 @@ import javax.xml.parsers.ParserConfigurationException;
import org.apache.catalina.Lifecycle;
import org.apache.catalina.LifecycleEvent;
import org.apache.catalina.LifecycleListener;
-import org.apache.catalina.startup.SafeForkJoinWorkerThreadFactory;
import org.apache.catalina.Server;
+import org.apache.catalina.startup.SafeForkJoinWorkerThreadFactory;
import org.apache.juli.logging.Log;
import org.apache.juli.logging.LogFactory;
import org.apache.tomcat.util.ExceptionUtils;
@@ -56,6 +56,8 @@ import org.w3c.dom.ls.DOMImplementationLS;
* Locked files usually occur when a resource inside a JAR is accessed without
* first disabling Jar URL connection caching. The workaround is to disable
this
* caching by default.
+ *
+ * This listener must only be nested within {@link Server} elements.
*/
public class JreMemoryLeakPreventionListener implements LifecycleListener {
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[tomcat] branch 9.0.x updated: Fix back-port of previous commit
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch 9.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/9.0.x by this push:
new d3f3e7f Fix back-port of previous commit
d3f3e7f is described below
commit d3f3e7fff77d83ecb672d513e857e1cac306cb69
Author: Mark Thomas
AuthorDate: Tue Nov 2 12:03:39 2021 +
Fix back-port of previous commit
---
java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java
b/java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java
index 12bf11e..5163623 100644
--- a/java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java
+++ b/java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java
@@ -32,8 +32,8 @@ import javax.xml.parsers.ParserConfigurationException;
import org.apache.catalina.Lifecycle;
import org.apache.catalina.LifecycleEvent;
import org.apache.catalina.LifecycleListener;
-import org.apache.catalina.startup.SafeForkJoinWorkerThreadFactory;
import org.apache.catalina.Server;
+import org.apache.catalina.startup.SafeForkJoinWorkerThreadFactory;
import org.apache.juli.logging.Log;
import org.apache.juli.logging.LogFactory;
import org.apache.tomcat.util.ExceptionUtils;
@@ -56,6 +56,8 @@ import org.w3c.dom.ls.DOMImplementationLS;
* Locked files usually occur when a resource inside a JAR is accessed without
* first disabling Jar URL connection caching. The workaround is to disable
this
* caching by default.
+ *
+ * This listener must only be nested within {@link Server} elements.
*/
public class JreMemoryLeakPreventionListener implements LifecycleListener {
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[tomcat] branch 8.5.x updated: Fix back-port of previous commit
This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch 8.5.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/8.5.x by this push:
new 861ab24 Fix back-port of previous commit
861ab24 is described below
commit 861ab24ad00c9ad6e7a762b7475e87fd3af9ca05
Author: Mark Thomas
AuthorDate: Tue Nov 2 12:03:39 2021 +
Fix back-port of previous commit
---
java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java
b/java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java
index c8d4847..59e8ff7 100644
--- a/java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java
+++ b/java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java
@@ -32,8 +32,8 @@ import javax.xml.parsers.ParserConfigurationException;
import org.apache.catalina.Lifecycle;
import org.apache.catalina.LifecycleEvent;
import org.apache.catalina.LifecycleListener;
-import org.apache.catalina.startup.SafeForkJoinWorkerThreadFactory;
import org.apache.catalina.Server;
+import org.apache.catalina.startup.SafeForkJoinWorkerThreadFactory;
import org.apache.juli.logging.Log;
import org.apache.juli.logging.LogFactory;
import org.apache.tomcat.util.ExceptionUtils;
@@ -56,6 +56,8 @@ import org.w3c.dom.ls.DOMImplementationLS;
* Locked files usually occur when a resource inside a JAR is accessed without
* first disabling Jar URL connection caching. The workaround is to disable
this
* caching by default.
+ *
+ * This listener must only be nested within {@link Server} elements.
*/
public class JreMemoryLeakPreventionListener implements LifecycleListener {
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[tomcat] branch 10.0.x updated: Fix BZ 65661. Add note on new direct memory reqs for multi-part upload
This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch 10.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/10.0.x by this push: new f7bf44a Fix BZ 65661. Add note on new direct memory reqs for multi-part upload f7bf44a is described below commit f7bf44a44d49cb5c0cf180140b58fffe9861a514 Author: Mark Thomas AuthorDate: Tue Nov 2 13:58:29 2021 + Fix BZ 65661. Add note on new direct memory reqs for multi-part upload https://bz.apache.org/bugzilla/show_bug.cgi?id=65661 Need at least multipart size limit * max. concurrent uploads bytes of direct memory --- webapps/docs/changelog.xml | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/webapps/docs/changelog.xml b/webapps/docs/changelog.xml index 28340f1..5d26791 100644 --- a/webapps/docs/changelog.xml +++ b/webapps/docs/changelog.xml @@ -373,8 +373,12 @@ 1.16-SNAPSHOT). Minor refactoring. (markt) -Update the internal fork of Apache Commons FileUpload to 33d2d79 -(2021-09-01, 2.0-SNAPSHOT). Refactoring and code clean-up. (markt) +65661: Update the internal fork of Apache Commons FileUpload +to 33d2d79 (2021-09-01, 2.0-SNAPSHOT). Refactoring and code clean-up. As +a result of Commons File Upload now using +java.nio.file.Files, 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. (markt) Update the internal fork of Apache Commons Pool to 2.11.1 (2021-08-17). - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[tomcat] branch main updated: Fix BZ 65661. Add note on new direct memory reqs for multi-part upload
This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/main by this push: new 6cf20b4 Fix BZ 65661. Add note on new direct memory reqs for multi-part upload 6cf20b4 is described below commit 6cf20b4a83f1e5b2ae86525b6b96389e801776b2 Author: Mark Thomas AuthorDate: Tue Nov 2 13:58:29 2021 + Fix BZ 65661. Add note on new direct memory reqs for multi-part upload https://bz.apache.org/bugzilla/show_bug.cgi?id=65661 Need at least multipart size limit * max. concurrent uploads bytes of direct memory --- webapps/docs/changelog.xml | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/webapps/docs/changelog.xml b/webapps/docs/changelog.xml index 0b768b4..691cd55 100644 --- a/webapps/docs/changelog.xml +++ b/webapps/docs/changelog.xml @@ -480,8 +480,12 @@ 1.16-SNAPSHOT). Minor refactoring. (markt) -Update the internal fork of Apache Commons FileUpload to 33d2d79 -(2021-09-01, 2.0-SNAPSHOT). Refactoring and code clean-up. (markt) +65661: Update the internal fork of Apache Commons FileUpload +to 33d2d79 (2021-09-01, 2.0-SNAPSHOT). Refactoring and code clean-up. As +a result of Commons File Upload now using +java.nio.file.Files, 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. (markt) Update the internal fork of Apache Commons Pool to 2.11.1 (2021-08-17). - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[tomcat] branch 9.0.x updated: Fix BZ 65661. Add note on new direct memory reqs for multi-part upload
This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch 9.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/9.0.x by this push: new 378919c Fix BZ 65661. Add note on new direct memory reqs for multi-part upload 378919c is described below commit 378919cb62af9fa3fcaf963ccffbadc0781de22b Author: Mark Thomas AuthorDate: Tue Nov 2 13:58:29 2021 + Fix BZ 65661. Add note on new direct memory reqs for multi-part upload https://bz.apache.org/bugzilla/show_bug.cgi?id=65661 Need at least multipart size limit * max. concurrent uploads bytes of direct memory --- webapps/docs/changelog.xml | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/webapps/docs/changelog.xml b/webapps/docs/changelog.xml index d6e647c..3e674a9 100644 --- a/webapps/docs/changelog.xml +++ b/webapps/docs/changelog.xml @@ -373,8 +373,12 @@ and DataSource testing. (remm) -Update the internal fork of Apache Commons FileUpload to 33d2d79 -(2021-09-01, 2.0-SNAPSHOT). Refactoring and code clean-up. (markt) +65661: Update the internal fork of Apache Commons FileUpload +to 33d2d79 (2021-09-01, 2.0-SNAPSHOT). Refactoring and code clean-up. As +a result of Commons File Upload now using +java.nio.file.Files, 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. (markt) Update the internal fork of Apache Commons Pool to 2.11.1 (2021-08-17). - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[tomcat] branch 8.5.x updated: Fix BZ 65661. Add note on new direct memory reqs for multi-part upload
This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch 8.5.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/8.5.x by this push: new 718dd11 Fix BZ 65661. Add note on new direct memory reqs for multi-part upload 718dd11 is described below commit 718dd11a2d4282cd784c7ce42db87cba92984c8d Author: Mark Thomas AuthorDate: Tue Nov 2 13:58:29 2021 + Fix BZ 65661. Add note on new direct memory reqs for multi-part upload https://bz.apache.org/bugzilla/show_bug.cgi?id=65661 Need at least multipart size limit * max. concurrent uploads bytes of direct memory --- webapps/docs/changelog.xml | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/webapps/docs/changelog.xml b/webapps/docs/changelog.xml index 25dcc73..0dcbed0 100644 --- a/webapps/docs/changelog.xml +++ b/webapps/docs/changelog.xml @@ -315,8 +315,12 @@ 1.16-SNAPSHOT). Minor refactoring. (markt) -Update the internal fork of Apache Commons FileUpload to 33d2d79 -(2021-09-01, 2.0-SNAPSHOT). Refactoring and code clean-up. (markt) +65661: Update the internal fork of Apache Commons FileUpload +to 33d2d79 (2021-09-01, 2.0-SNAPSHOT). Refactoring and code clean-up. As +a result of Commons File Upload now using +java.nio.file.Files, 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. (markt) Update the internal fork of Apache Commons Pool to 0da5c54 - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
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.xm
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. checks are complete. If the application is marked as serviced when the method is called, the method will be a NO-OP. + In 10.0.11 onwards, as a result of the updated fork of Commons +FileUpload now using java.nio.file.Files, 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. + 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. blocked with a 403. Reference: AJP connector. + In 8.5.64 onwards, the semantics of the HostConfig.check(String) method have changed. Rather than marking the application as serviced before calling the method, the @@ -253,6 +254,11 @@ of Apache Tomcat. checks are complete. If the application is marked as serviced when the method is called, the method will be a NO-OP. + In 8.5.71 onwards, as a result of the updated fork of Commons +FileUpload now using java.nio.file.Files, 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. 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. cause a startup error if they are present in the configuration, but may produce a warning and will have no effect. + In 9.0.53 onwards, as a result of the updated fork of Commons +FileUpload now using java.nio.file.Files, 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. + 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. -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), +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. 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 re
[Bug 65661] 'OutOfMemoryError: Direct buffer memory' in DiskFileItem.get()
https://bz.apache.org/bugzilla/show_bug.cgi?id=65661 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Mark Thomas --- Thanks for the report. I have added a note to the change log for each of the affected versions and to the migration guide. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: November releases
On Tue, Nov 2, 2021 at 12:46 PM Mark Thomas wrote: > > Hi all, > > There doesn't seem to be much in the changelogs at the moment and the > code signing is currently unavailable as the renewal process is taking > longer than expected. Therefore, my current thinking is to delay the > release process and review the situation towards the end of the week. > > Thoughts? +1 Rémy - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: November releases
Mark, On 11/2/21 07:45, Mark Thomas wrote: Hi all, There doesn't seem to be much in the changelogs at the moment and the code signing is currently unavailable as the renewal process is taking longer than expected. Therefore, my current thinking is to delay the release process and review the situation towards the end of the week. Thoughts? +1 I was thinking the same thing (not much to release). -chris - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
