Am 01.05.26 um 22:53 schrieb Mark Thomas:
The proposed Apache Tomcat 11.0.22 release is now available for voting.
The notable changes compared to 11.0.21 include:
- Enhance version.sh and version.bat to display APR, Tomcat Native, and
OpenSSL version information.
- Free private keys, keys and certificates after use in FFM based
connector configuration.
- Various HTTP/2 validation improvements and a broader change to use
stream resets rather than connection closures where appropriate.
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.22/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1590
The tag is:
https://github.com/apache/tomcat/tree/11.0.22
ccdf7a8c736bde0f4875a10667b21cddbd4be21f
The proposed 11.0.22 release is:
[ ] -1 Broken - do not release
[ ] +1 Stable - go ahead and release as 11.0.22
I will report soon about my (positive full tests), but one annoyance was
observed here: the new improved version reporting throws an exceptopn if
libssl.so can not be found. On a non-dev Linux system, the file
libssl.so is typically not installed, because it is only needed for
compile-limking. The file, that exists, is
/usr/lib/x86_64-linux-gnu/libssl.so.3. But that file is not, what is
needed here:
$ bin/version.sh
Using CATALINA_BASE: /path/to/output/build
Using CATALINA_HOME: /path/to/output/build
Using CATALINA_TMPDIR: /path/to/output/build/temp
Using JRE_HOME: /home/jung
Using CLASSPATH:
/path/to/output/build/bin/bootstrap.jar:path/to/output/build/bin/tomcat-juli.jar
Using CATALINA_OPTS:
Server version: Apache Tomcat/11.0.23-dev
Server built: May 3 2026 10:56:28 UTC
Server number: 11.0.23.0
OS Name: Linux
OS Version: 6.8.0-111-generic
Architecture: amd64
JVM Version: 22.0.1+8-16
JVM Vendor: Oracle Corporation
APR loaded: false
Mai 04, 2026 7:52:19 PM
org.apache.catalina.core.OpenSSLLifecycleListener isAvailable
SCHWERWIEGEND: OpenSSL initialization failed
java.lang.ExceptionInInitializerError
at
org.apache.tomcat.util.net.openssl.panama.OpenSSLLibrary.initLibrary(OpenSSLLibrary.java:86)
at
org.apache.tomcat.util.net.openssl.panama.OpenSSLLibrary.init(OpenSSLLibrary.java:179)
at
java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)
at
org.apache.catalina.core.OpenSSLLifecycleListener.isAvailable(OpenSSLLifecycleListener.java:58)
at
java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)
at org.apache.catalina.util.ServerInfo.main(ServerInfo.java:201)
Caused by: java.lang.IllegalArgumentException: Cannot open library:
libssl.so
at
java.base/java.lang.foreign.SymbolLookup.libraryLookup(SymbolLookup.java:314)
at
java.base/java.lang.foreign.SymbolLookup.libraryLookup(SymbolLookup.java:266)
at org.apache.tomcat.util.openssl.openssl_h.<clinit>(openssl_h.java:94)
... 8 more
Third-party libraries:
ecj-4.39.jar: 3.45.0.v20260224-0835
jakartaee-migration-1.0.10-shaded.jar: 1.0.10
This seems not to occur during the usual startup logging. So IMHO is is
just an annoyance (concerning only version.sh) and not a show-stopper.
Best regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
