Ace8 is the modernization practice of AceMQ.24/7 support from AceMQ after go-live
Book an Assessment

On this page

  • Tomcat
  • Jakarta EE
  • Java
  • Spring Boot
  • OpenRewrite
  • Spring
  • AWS Transform
  • JBoss EAP
  • Tomcat
  • Jakarta EE
  • Java
  • Spring Boot
  • OpenRewrite
  • Spring
  • AWS Transform
  • JBoss EAP
The short answer

To upgrade Tomcat 9, move each application to Tomcat 10.1 or Tomcat 11, which use the jakarta.* namespace instead of javax.*. A Tomcat 9 WAR will not run unchanged on either, so every application and its libraries must be migrated, in source with OpenRewrite or in bytecode with Apache's migration tool. Choose 11 if you can run Java 17 or later, and 10.1 if you must stay on Java 11.

ServiceJava upgradeWhat breaks, what a recipe can fix, and what needs a person.See the service

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.

VersionServlet specNamespaceMinimum Java
Tomcat 9.0Servlet 4.0javaxJava 8
Tomcat 10.1Servlet 6.0jakartaJava 11
Tomcat 11.0Servlet 6.1jakartaJava 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.

tomcat-9-upgrade-review.mdEngineer review
Findings
F-01Your own code: imports, annotations and descriptors.
F-02Libraries that touch the servlet API, JSP tags, JPA or Bean Validation. Each needs a jakarta-compatible release; the ones with none set the schedule.
F-03Spring: Spring Boot 2 and Spring Framework 5 use javax. Spring Boot 3 and Spring Framework 6 use jakarta and need Java 17. See Spring Boot 3 migration.
F-04Third-party WARs you cannot change, which need the bytecode route below.
Illustrative sample, not a real client report

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:

01

Tomcat 11 removed support for configuring a Security Manager, because Jakarta EE 11 dropped it. Remove any -Djava.security.manager setup before the move.

02

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.

03

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.

04

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.

Step 01 of 05

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.

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

A rough guide to scope, not a price
Effort positionQualitative
Typical
LighterTypicalHeavier
Pushing the scope up
Nothing at the top setting
PriceQuote on request
Get a fixed price in the assessment

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.

01

Source migration to jakarta for active applications.

02

Migration tool for stable third-party or legacy applications you will not change.

03

Spring Boot 3 with embedded Tomcat 10.1 or later for container targets.

04

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.

VersionServlet specNamespaceMinimum JavaStatus (checked 17 Nov 2026)Source
Tomcat 11.0Servlet 6.1jakartaJava 17Supported, no end date announcedWhich version do I want?
Tomcat 10.1Servlet 6.0jakartaJava 11Supported, no end date announcedWhich version do I want?
Tomcat 10.0Servlet 5.0jakartaJava 8Ended 31 Oct 2022Which version do I want?
Tomcat 9.0Servlet 4.0javaxJava 8End of support expected no earlier than 31 Mar 2027Apache Tomcat home page
Tomcat 8.5Servlet 3.1javaxJava 7Ended 31 Mar 2024Which version do I want?

08 · Next step

How does Ace8 run a Tomcat 9 upgrade?

Ace8 is the modernization practice of AceMQ.

  1. 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.

  2. 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.

FAQ

Frequently asked questions

Short answers to what buyers ask first. Something else on your mind? Ask an engineer.

Tomcat 11 if your applications can run on Java 17 or later, or Tomcat 10.1 if they must stay on Java 11. Apache lists no end date for either as of 17 Nov 2026.

Start here

Know the cost before anything moves.

A fixed-price assessment gives you the inventory, the risk score and a phased plan. Scope and cost are fixed before the migration starts.

Inventory
Every application, its stack and what it depends on.
Risk score
Where a change is likely to break, ranked.
Phased plan
What moves first, which tools lead, and the fixed price.

Get in touch

Talk to a modernization engineer.

Tell us what you run today. An engineer, not a sales script, replies within one business day.

305-204-2607info@ace8.io

66 W. Flagler St. 9th Floor
Miami, FL 33130

What are you moving off? *

Fixed price. Scope and cost before any migration starts.