Am 04.05.26 um 20:21 schrieb Coty Sutherland:
Hi Rainer,
Oh, shoot. Thanks for catching that. I'll look into it ASAP.
I have some additional comments. Sorry about not thinking earlier about it.
- APR, FFM: I think ServerInfo.main() tries to load APR and OpenSSL and
shows the resulting info. That is not necessarily the same info, that
describes the runtime status of Tomcat. For Tomcat it depends on whether
and how the corresponding listeners are configured in server.xml. Since
the nice thing about version.sh is, that it is simple and does not need
to parse server.xml, IMHO it would be best to surround the APR and
OpenSSL info output with a short text, that informs the user, that these
features are available, but may not be activated in server.xml.
- third-party jars: A future improvement could be, to also check
catalina.base/lib if catalina.base != catalina.home. In that case,
Tomcat jars located there would overwrite the ones shipped in
catalina.home (Patching or old forgotten patches) and third-party libs
would be used just like the ones in catalina.home (see common.loader in
conf/catalina.properties(, Another info could be the number of classes
deployed directly in catalina.home and catalina.base respectively (in an
exploded class tree). The latter is very uncommon nowadays but could
again be used for patching a few classes.
Thanks for the improvement nevertheless!
Best regards,
Rainer
On Mon, May 4, 2026 at 2:15 PM Rainer Jung <[email protected]> wrote:
Hi Coty,
the new feature throws an exception when bin/version.sh (probably also
version.bat) is called with Java 22+ (FFM support) but no libssl.so
installed (for install not libssl-dev package).
See my message in the 11.0.23 vote thread.
Best regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
