Re: Apache Tomcat 9.1.x release timeframe
"Sebastian Trost via users" <[email protected]> Fri, 17 Jul 2026 17:27:08 +0200
| Newsgroups | gmane.comp.jakarta.tomcat.user |
|---|---|
| Message-ID | <[email protected]> |
Eddie, On 7/17/26 16:57, Eddie Rowe via users wrote: > The helpful links posted again indicate there will be a "few weeks" of overlap between the release of 9.1 and the EOL of 9.0. Does a "few weeks" mean 2 weeks or does it mean like 8 weeks? I can appreciate this 9.1 being treated like a normal maintenance release in the 9.0.x series but I don't think there is an appreciation that upgrading to those minor releases can be painful for some of us. (Ignoring for the moment that some are using connectors that are being removed in 9.1 which breaks things for us.) Each release of Tomcat, despite the hard work of several persons, has bugs. If the first release of 9.1 has a bug that affects someone they might have to stay on 9.0.x and if 9.1 corrects a security issue that puts people in a difficult position. > I quote the official documentation here: "The differences between 9.0.x and 9.1.x will be minimal and users can start making the necessary transition now." The first version of 9.1 will probably not correct a security issue. The point is to release a 9.1 version which is, as quoted, minimally different than the last 9.0 version - only missing the APR connectors and Tomcat Native 1.3.x support. > And there are going to be more than a few persons who try to upgrade only to learn their AJP connectors no longer work. 8-( Only the APR connectors are being removed. NIO and NIO2 will still support AJP. If you are aware of the EOL and update Tomcat to 9.1.x as soon it has been released, you also should be aware WHY there is a 9.1 release. I doubt that people, who still use the APR connectors are the first ones who update to the latest Tomcat and breaking their deployments. But IF that would be the case, the remedy to that is an easy search and replace of a string within the server.xml. Sebastian