01 · Targets
Should you upgrade Tomcat 9 to 10.1 or to 11?
Upgrade to Tomcat 11 if your applications can run on Java 17 or later, and to Tomcat 10.1 if they must stay on Java 11. Both implement Jakarta EE, so the code change is the same for either target.
| Version | Servlet spec | Namespace | |
|---|---|---|---|
| Tomcat 9.0 | Servlet 4.0 | javax | Java 8 |
| Tomcat 10.1 | Servlet 6.0 | jakarta | Java 11 |
| Tomcat 11.0 | Servlet 6.1 | jakarta | Java 17 |
02 · The catch
What breaks when you move from Tomcat 9 to 10.1 or 11?
Everything that imports a javax servlet, JSP, JPA or Bean Validation package breaks, because Jakarta EE renamed those packages to jakarta.*. A WAR built for Tomcat 9 will not run on Tomcat 10.1 or 11 until its code and its libraries use the new names. See javax to Jakarta migration.
03 · Configuration
What changes in Tomcat configuration when you leave version 9?
The server configuration needs a review, not a rewrite, and the points to check are small and listed in Apache's migration guides for each version. The changes to look for:
Tomcat 11 removed support for configuring a Security Manager, because Jakarta EE 11 dropped it. Remove any -Djava.security.manager setup before the move.
Tomcat 10.1 needs Java 11 or later and Tomcat 11 needs Java 17 or later, so the JDK, service scripts and container images change with it.
Custom valves, realms and listeners compiled against Tomcat 9 internals need rebuilding against the new version, and any that import javax classes need the rename.
Compare server.xml, context.xml and web.xml defaults against the migration guide for the target version, and re-test connectors and TLS settings.
04 · Method
How do you move each application to Tomcat 10.1 or 11 with OpenRewrite?
Move one application at a time: run the javax to jakarta recipe, build, test and deploy to the new Tomcat, with the Tomcat 9 instance kept for rollback. OpenRewrite has a recipe for the rename (org.openrewrite.java.migrate.jakarta.JavaxMigrationToJakarta), and AI-assisted tools such as AWS Transform can cover what it misses.
Inventory
List every application on Tomcat 9 with its Java and Spring versions. Applications on Java 8 have two upgrades to make; see Java 8 upgrade.
Library check
Find the jakarta-compatible release of each library that touches javax packages.
Rename with a recipe
Run the OpenRewrite recipe, then review the diff. It rewrites imports, descriptors and annotations.
Test
Run the full test suite and a load test on the new Tomcat, not just on the old one.
Cut over
Move one application at a time behind the load balancer.
05 · Effort
What drives the effort of a Tomcat 9 upgrade?
Effort follows the libraries and the test coverage of each application. A fixed-price assessment gives a per-application estimate. The drivers:
Libraries with no jakarta-compatible release
Spring Boot 2 applications that also need the Java 17 move
Test coverage, and whether a load test exists
Custom valves, realms and listeners
Third-party WARs where the migration tool is the only route
The number of applications sharing a Tomcat instance, since each must move together or be split out first
06 · Decision
Should you upgrade Tomcat or move the application to Spring Boot?
Upgrade the server for applications that are stable, and move to Spring Boot 3 with embedded Tomcat for applications you will keep developing or want in containers. Rewrite only where the application design is the blocker.
Source migration to jakarta for active applications.
Migration tool for stable third-party or legacy applications you will not change.
Spring Boot 3 with embedded Tomcat 10.1 or later for container targets.
See Tomcat vs JBoss if you are deciding whether Tomcat is still the right server.
07 · Reference
Support dates by vendor
Dates read on tomcat.apache.org on 17 Nov 2026. Tomcat Native 1.3.x has the same date as Tomcat 9. Apache is the source for every date above; confirm before you plan around one.
Need to stay on Tomcat 9 for now? OSSeva covers that.
| Version | Servlet spec | Namespace | Status (checked 17 Nov 2026) | Source | |
|---|---|---|---|---|---|
| Tomcat 11.0 | Servlet 6.1 | jakarta | Java 17 | Supported, no end date announced | Which version do I want? |
| Tomcat 10.1 | Servlet 6.0 | jakarta | Java 11 | Supported, no end date announced | Which version do I want? |
| Tomcat 10.0 | Servlet 5.0 | jakarta | Java 8 | Ended 31 Oct 2022 | Which version do I want? |
| Tomcat 9.0 | Servlet 4.0 | javax | Java 8 | End of support expected no earlier than 31 Mar 2027 | Apache Tomcat home page |
| Tomcat 8.5 | Servlet 3.1 | javax | Java 7 | Ended 31 Mar 2024 | Which version do I want? |
08 · Next step
How does Ace8 run a Tomcat 9 upgrade?
Ace8 is the modernization practice of AceMQ.
- 01
AceMQ engineers run the javax to jakarta rename with recipes, use AI-assisted tools on what the recipes miss, and review every change against your tests. AceMQ supports the upgraded stack after go-live.
- 02
Get a Java upgrade estimate through the modernization assessment, which lists every Tomcat 9 application, its blockers and a target. The Java upgrade service describes the delivery.