I think there may be multiple issues with reproducibility.
I'm investigating now...
Can I suggest holding off on tagging 10.1.x and 9.0.x for now. I should
have got to the bottom of this in the next hour or so.
Mark
On 09/11/2026 09:48, Mark Thomas via dev wrote:
The proposed Apache Tomcat 11.0.28 release is now available for voting.
The notable changes compared to 11.0.27 include:
- Large number of bugfixes to jdbc-pool
- The JAAS realm is now deprecated and will be removed in Tomcat 12
- Deprecate the EncryptInterceptor and replace it with TLS-PSK support
to encrypt cluster traffic
For full details, see the change log:
https://nightlies.apache.org/tomcat/tomcat-11.0.x/docs/changelog.html
Applications that run on Tomcat 9 and earlier will not run on Tomcat 11
without changes. Java EE applications designed for Tomcat 9 and earlier
may be placed in the $CATALINA_BASE/webapps-javaee directory and Tomcat
will automatically convert them to Jakarta EE and copy them to the
webapps directory. Applications using deprecated APIs may require
further changes.
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-11/v11.0.28/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1611
The tag is:
https://github.com/apache/tomcat/tree/11.0.28
247b2995eb6e5be84f7af015160fd08b88270bfd
The proposed 11.0.28 release is:
[ ] -1 Broken - do not release
[ ] +1 Stable - go ahead and release as 11.0.28
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
