Somasani,
On 4/16/26 4:27 AM, somasani nikhil wrote:
We are currently reviewing our application server roadmap and would
appreciate some clarification around *Tomcat 9.1 release and support plans*.
Based on the information shared in the following article:
https://tomcat.apache.org/tomcat-9.0.x-eos.html
our understanding is that *Tomcat 9.0.x will remain supported through March
2027*, and that there are plans for a *Tomcat 9.1.x* line. To help us plan
accordingly, we would appreciate guidance on the following:
1.
*Availability timeline*
- Is there an approximate availability timeframe for the *first Tomcat
9.1.x release*?
- Will 9.1.x overlap with 9.0.x support for a significant period?
No. We are likely to release our first 9.1.x version after the final
9.0.x release is made. We have roughly monthly releases of all supported
Tomcat versions, and I would expect that the first 9.1.x release will
follow the last 9.0.x release by about a month.
2.
*Upgrade considerations (9.0 → 9.1)*
- Are there any *major behavioral, compatibility, or configuration
changes* that users currently on Tomcat 9.0.x should be aware of when
planning a move to 9.1.x? (Except the fact for "APR/native connectors
for HTTP, HTTPS and AJP will not be available")
- Will 9.1.x remain fully *Java EE / javax‑based*, similar to 9.0.x?
These details are covered in the EOS notice that you posted above. the
entire reason for 9.1 to continue to exist is to support Java EE for
those who are not yet prepared to make a move to Jakarta EE.
Something not mentioned on that page is that the required version of
Java *might* be raised beyond the existing Java 8 requirement for Tomcat
9.0.
3.
*Support and lifecycle changes*
- Are there any *changes in support terms, maintenance policies, or
lifecycle expectations* between 9.0.x and 9.1.x that users should
factor into long‑term planning?
- Any guidance on recommended upgrade windows or best practices would
be helpful.
Upgrading from Tomcat 9.0.last to 9.1.first should require minimal effort:
1. Confirm you aren't using components being removed (APR)
2. Confirm minimum Java version
3. Follow your normal 9.0.x -> 9.0.y upgrade process
For our context, *Tomcat 10.x involves a Jakarta EE–based namespace and
significant structural changes*, which requires notable application‑level
work. As a result, we need to make near‑term decisions on whether to
continue on the 9.x line or plan for a larger migration, and clarity on
9.1.x would greatly help our SPM and release planning.
Any details, references, or forward‑looking guidance you can share would be
highly appreciated.
Tomcat 9.1 will continue exist for just the situation you find yourself in.
I would recommend moving toward Jakarta EE for your long-term plans, but
for the next few years, you should be able to rely on the existence of
Tomcat 9.1 being supported.
Please note that Tomcat 10.1 and later includes an automatic migration
facility during deployment. You might want to see if your application
will run under Tomcat 10.1 without any changes just by using this
automated migration facility. You may find that you are closer to being
ready for a Jakarta EE migration than you realize. (Note that it will
migrate your application *and* all of its dependent libraries.)
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
