On Thu, Nov 12, 2026, 2:31 PM Christopher Schultz <
[email protected]> wrote:

> Coty,
>
> On 11/10/26 8:44 PM, Coty Sutherland via dev wrote:
> > On Mon, Nov 9, 2026 at 4:37 PM Rémy Maucherat via dev <
> [email protected]>
> > wrote:
> >
> >> The proposed Apache Tomcat 9.0.124 release is now available for voting.
> >>
> >> The notable changes compared to 9.0.123 are:
> >>
> >> - 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 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.124/
> >>
> >> The Maven staging repo is:
> >> https://repository.apache.org/content/repositories/orgapachetomcat-1613
> >>
> >> The tag is:
> >> https://github.com/apache/tomcat/tree/9.0.124
> >> 6a78f8c622f03f7d8abef0179c85d958de000475
> >>
> >> The proposed 9.0.124 release is:
> >> [ ] -1, Broken - do not release
> >> [x] +1, Stable - go ahead and release as 9.0.124
> >>
> >
> > LGTM, except for all of the APR tests failing when you run with
> > tomcat-native v2 loaded. Rather than not testing with v2, I'll try to
> tweak
> > the build.xml to skip the APR tests when tomcat-native >= 2 is used.
> Tomcat 9.0.x should work with tcnative 2.x. It's the upgrade path we're
> pushing to everyone freaking out about 9.1.x.
>
> What's going wrong in your test environment?
>

The APR failures are expected since there's no support in v2, but I also
had unsatisfied link errors in NIO/2 which was due to the older version of
tcnative v2 (2.0.15) not being compatible. See
https://lists.apache.org/thread.html/f6051nd2gg9h9qtpo4bznhsmtp8twndm


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

Reply via email to