Back to all use cases

ConsultingCross-Industry

Find the libraries that block the jakarta move before the 9.0.x support date forces it

Engineering Organization

A typical consulting engagement for a team running Java EE 8 web applications on Tomcat 9: a scan of every javax reference, a conversion rehearsal on a copy and a cutover plan with the old server as the rollback.

Tomcat consulting

Overview

A typical engagement starts with a team that runs a dozen Java EE 8 web applications on Tomcat 9. Apache has announced that support for Tomcat 9.0.x ends on 31 March 2027, and the team knows the move to 10.1 or 11 renames javax to jakarta but not how many of its libraries are ready.

Challenge

Tomcat 10 and later use the jakarta namespace where Tomcat 9 uses javax, so an application that compiles and runs on 9 fails with ClassNotFoundException or NoClassDefFoundError on 10.1. The failure does not come from the application's own code alone: older libraries, application server extensions and bytecode agents carry javax references too. Tomcat 10.1 needs Java 11 and Tomcat 11 needs Java 17, which adds a Java move to the same plan.

Environment

Several Java EE 8 web applications built as WAR files on Tomcat 9.0.x, on Java 8 and 11, behind a load balancer, with a mix of virtual machines and container images.

Approach

AceMQ engineers scan each WAR and its libraries for javax references and sort the findings into code the team owns, libraries that have Jakarta builds and libraries that do not. They run Apache's migration tool for Jakarta EE on a copy of one application as a first conversion, deploy it on Tomcat 10.1 in a rehearsal environment with the same thread pools, TLS settings and proxy, and record every failure. The report orders the applications by risk and writes the cutover and rollback for each. The engagement covers the platform move, not changes to business logic.

Solution

  1. Inventory of applications by Tomcat line, Java version and framework
  2. Scan of WARs and libraries for javax references, sorted by who owns the fix
  3. First conversion with the Tomcat migration tool for Jakarta EE on one application, with every failure recorded
  4. Library replacement list with Jakarta builds and the ones that have none
  5. Java upgrade steps to 11 or 17, tested one at a time
  6. Cutover plan per application with the old Tomcat kept as the rollback

Outcome

The engagement delivers the inventory, a ranked list of blockers, a converted pilot application, a Java and Tomcat path per application and a rollback for each cutover. The team's own developers make any code changes the blockers require, and AceMQ can run the first cutovers with them. Oracle Java licensing questions stay with the customer's agreements and counsel.

Technologies

Apache TomcatJavaDocker

Need Apache Tomcat Architecture Guidance?

AceMQ's senior Apache Tomcat engineers have handled this exact type of engagement before. Whether you need architectural guidance, hands-on remediation, or an ongoing managed partnership, we're ready to help.