Skip to main content
umair14
Level 1
Nov 17, 2026 11:04 PM UTC
Question

Official AEM 6.5 Support for Apache Tomcat 9.0.x and Roadmap for Tomcat 9.1?

Hi everyone,

I am looking for clarification regarding official support for Apache Tomcat 9.0.x and Tomcat 9.1 with AEM 6.5.

Currently, the AEM 6.5 Technical Requirements and Deploying Guide only lists restricted support for Tomcat 8.5.x (which is already end-of-life). Since Tomcat 9.0.x was released in September 2017, I wanted to check if the documentation simply hasn't been updated or if there are specific limitations.

  1. Tomcat 9.0.x Support: Is Apache Tomcat 9.0.x officially supported for AEM 6.5 (including recent Service Packs)? Has anyone successfully upgraded to or deployed AEM 6.5 on Tomcat 9 in production?
  2. Tomcat 9.1 Roadmap: Community support for Apache Tomcat 9.0.x reaches End of Life on March 31, 2027. Apache has announced that a follow-on branch, Tomcat 9.1 (without APR/native connectors), will be released to extend support for applications still relying on javax.* packages through December 2030. Is there any roadmap or plan from Adobe to officially support Tomcat 9.1 for AEM 6.5?

Any insights, official updates, or real-world deployment experiences would be greatly appreciated.

Thanks in advance!

1 reply

Mani_kumar_
Community Advisor
Community Advisor
Nov 18, 2026 5:32 AM UTC

Hi @umair14,

 

Short answer: no on both counts — Tomcat 9.0.x is not officially supported on AEM 6.5, and Adobe has published no plan to support Tomcat 9.1. The documentation is current, not out of date.

 

**1. Tomcat 9.0.x on AEM 6.5 — not supported**

The AEM 6.5 Technical Requirements (updated Oct 9, 2026) list exactly one Tomcat version for 6.5: **Apache Tomcat 8.5.x**, at Restricted Support for new contracts. Tomcat 9.0.x does not appear in the matrix at all — not even as "not supported" — which means Adobe makes no statement about whether it works and does not support it. The same applies to 6.5 LTS: its Technical Requirements (updated Sep 29, 2026) list only **Tomcat 10.0.x/10.1.x**, also Restricted. So there is no supported Tomcat 9.0.x path on either branch, including on the recent service packs. If you run AEM 6.5 on Tomcat 9 in production and hit an issue, Adobe can ask you to reproduce it on a supported configuration (the quickstart JAR with built-in Jetty 9.4, fully supported, or Tomcat 8.5.x) before engaging — that is the practical cost of running outside the matrix.

 

Your observation about 8.5.x is correct and worth naming: Apache ended support for Tomcat 8.5.x in March 2024, yet it remains the listed Tomcat for AEM 6.5. Adobe certifies specific versions rather than tracking Apache's latest, and the listing is deliberate, not an oversight.

 

One more note on the matrix: all application-server deployments on both branches are Restricted Support for new contracts — existing customers can upgrade and keep using an application server, but new contracts come with support criteria and a support program. The quickstart JAR is the fully supported deployment.

 

**2. Tomcat 9.1 — real branch, no Adobe plan**

You are right about Apache's side: Tomcat 9.0.x reaches end of support on March 31, 2027, and Apache announced (Feb 11, 2026) a follow-on **9.1.x branch, due shortly before 9.0 support ends and supported until Dec 31, 2030**, for applications that still rely on `javax.*` — it drops the APR/native connectors and Tomcat Native 1.3.x. But Adobe has published no roadmap or plan to support Tomcat 9.1 on AEM 6.5 or 6.5 LTS: neither Technical Requirements page lists it, and Adobe's releases roadmap contains no Tomcat 9.1 entry. It also cannot be certified yet — the branch has not shipped. If your organisation needs 9.1 support, the route is a feature request through Adobe Support or your TAM, not the community roadmap.

 

**What I would plan around:** if a WAR deployment on Tomcat is a hard requirement, the supported path forward is 6.5 LTS on Tomcat 10.0.x/10.1.x with Java 17 or 21 — noting that Tomcat 10 uses the `jakarta.*` namespace, so it is an application migration off `javax.*`, not a server swap. If you must stay on `javax.*` past March 2027, that is exactly the case to put to Adobe Support now, while 9.1 is still pre-release.

 

**How to verify:** the matrices are the source of truth — AEM 6.5 Technical Requirements and AEM 6.5 LTS Technical Requirements on Experience League. After any change, confirm the running Tomcat version in the startup log.

Translate