Rémy,

Thanks for RMing.

On 3/30/26 2:34 PM, Rémy Maucherat wrote:
The proposed Apache Tomcat 9.0.117 release is now available for voting.

The notable changes compared to 9.0.116 are:

- Fix a bug in the non-blocking flushing code for NIO+TLS that meant
    that a response may not have been fully written until the connection
    was closed. Pull request 966 provided by Phil Clay.

- Improved HTTP/2 error handling

- Better error handling for the EncryptInterceptor

For full details, see the changelog:
https://nightlies.apache.org/tomcat/tomcat-9.0.x/docs/changelog.html

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.117/

The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1587

The tag is:
https://github.com/apache/tomcat/tree/9.0.117
f892e52577feef83aff57d34c2b4be61a5a68524

The proposed 9.0.117 release is:
[ ] -1, Broken - do not release
[ ] +1, Stable - go ahead and release as 9.0.117

+1 for stable release.

The build is 100% reproducible and all the unit tests pass on MacOS aarch64. I lost the complete log but here are the environmental details:

* Environment
* Java (build): openjdk version "25.0.2" 2026-01-20 LTS OpenJDK Runtime Environment Temurin-25.0.2+10 (build 25.0.2+10-LTS) OpenJDK 64-Bit Server VM Temurin-25.0.2+10 (build 25.0.2+10-LTS, mixed mode, sharing) * Java (test): openjdk version "25.0.2" 2026-01-20 LTS OpenJDK Runtime Environment Temurin-25.0.2+10 (build 25.0.2+10-LTS) OpenJDK 64-Bit Server VM Temurin-25.0.2+10 (build 25.0.2+10-LTS, mixed mode, sharing) * Ant: Apache Ant(TM) version 1.10.15 compiled on August 25 2024
*  OS:              Darwin 25.3.0 arm64
*  cc:              Apple clang version 17.0.0 (clang-1700.6.4.2)
*  make:            GNU Make 3.81
* OpenSSL: OpenSSL 3.6.0 1 Oct 2025 (Library: OpenSSL 3.6.0 1 Oct 2025)
*  APR:             1.7.6

-chris


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to