01
Emergency Incident Response
Server down, requests hanging, out of memory, or failing after a patch. A senior engineer joins a live bridge within 15 minutes, 24/7, with access to diagnose, not a ticket acknowledgement.
Apache Tomcat Support
24/7 Apache Tomcat Support with Emergency Response and Patches
AceMQ provides 24/7 Apache Tomcat support for Tomcat 8.5, 9, 10.1 and 11, standalone or embedded in a Spring Boot application, with a senior engineer on a live bridge within 15 minutes of a P1. Apache ends support for Tomcat 9.0.x on 31 March 2027; AceMQ delivers patched 9.0 builds after that date, as it already does for 8.5 and 10.0. We also plan the upgrade path from Java 8 to 21 and from Tomcat 9 to 10.1 or 11.
Support quotes answered within 1 hour, by a senior engineer.
- min emergency SLA
- 15
- global coverage
- 24/7
- enterprise customers
- 130+
- countries served
- 26+
Customers
Partners
Incident Triage
Apache Tomcat problems we fix every week
These are real symptoms from real Apache Tomcat production environments — and the first thing our engineers check when one comes in.
| Symptom you're seeing | What we check first | Typical resolution |
|---|---|---|
| Requests hang and everything times out while CPU is idle | A thread dump (jstack or jcmd) to see whether the connector threads are all parked. Usually the request pool (maxThreads) is used up by calls waiting on a database pool, a slow downstream service or a lock, so we trace the blocked frames back to the resource they wait on. | Pool and timeout settings, plus the blocking call |
| OutOfMemoryError for Metaspace or heap after a few redeploys | Heap histograms and a heap dump compared across redeploys. A hot redeploy leaves the old web application class loader pinned by a ThreadLocal, a JDBC driver registered with a shared class loader, or a thread the application started and never stopped. Tomcat logs the likely culprit at undeploy as a memory leak warning. | Application fix, then clean redeploys |
| "Cannot get a connection, pool error Timeout waiting for idle object" | Pool size against load, then leaked connections. We turn on abandoned-connection logging in a test run to find the code path that never closes a connection, and compare the pool maximum with the database's own connection limit. | Code fix, then pool sizing |
| Intermittent 502 or connection reset errors behind a load balancer | The connector's keepAliveTimeout and connectionTimeout against the balancer's idle timeout. If Tomcat closes an idle connection before the balancer does, the next request on that connection fails. Forwarded-header handling (RemoteIpValve) comes next. | Connector timeouts aligned with the balancer |
| ClassNotFoundException for javax.servlet, or NoClassDefFoundError for jakarta.servlet, after an upgrade | Tomcat 10 and later use the jakarta.* namespace, and Tomcat 9 uses javax.*. We scan the WAR and its libraries for the wrong namespace, then convert them with the Tomcat migration tool for Jakarta EE or move the dependencies to Jakarta builds. | Namespace migration, tested before cutover |
| TLS handshake failures after a Java upgrade | The JDK's disabled algorithms list (jdk.tls.disabledAlgorithms) against the protocols and ciphers set on the connector's SSLHostConfig and what the clients offer. Newer JDK builds switch off older TLS versions and weak algorithms, so a client that connected last month stops. | Connector TLS settings or a client update |
| A scanner flags the Tomcat version, or the AJP connector | Which CVEs apply to your exact version and connector configuration. The AJP connector is a common flag: Tomcat 9.0.31 hardened its default configuration in response to CVE-2020-1938 (Ghostcat), and older configurations often never changed. | Patch, or a configuration change that removes the exposure |
| The container is killed for exceeding its memory limit, or startup is slow | The container memory limit against heap plus Metaspace, thread stacks and direct buffers, because the JVM uses more than -Xmx. For slow startup we look at JAR scanning, which Tomcat can be told to skip for libraries that carry no annotations or TLDs. | JVM and container settings |
Resolution times reflect typical Apache Tomcat engagements under an active AceMQ support contract. Every P1 closes with a written root-cause analysis.
What's Included
Everything in your Apache Tomcat support contract
No add-on pricing for incidents. No per-ticket charges. One contract covers the whole surface.
- 02
Patched Builds Past Apache Support
Apache ends support for Tomcat 9.0.x on 31 March 2027. AceMQ delivers patched 9.0 builds after that date, as it does today for 8.5 and 10.0: CVE fixes backported from supported branches, shipped as signed Docker images, packages or zip archives.
- 03
CVE & Patch Advisory
Tomcat CVE alerts for your exact version and connector set-up, a view on whether your configuration is exposed, and a tested path to the fix. Useful when a scanner or an auditor sends you a list.
- 04
Java and Tomcat Upgrade Path
Java 8 to 11, 17 and 21, and Tomcat 9 to 10.1 or 11, in the order your applications can take them. That includes the javax to jakarta namespace migration, rehearsed on a copy of production before it touches live traffic.
- 05
Root Cause Analysis
Every P1 closes with a written RCA: what failed, why, the fix applied, and the configuration, code or JVM change that prevents recurrence. Delivered as standard, not on request.
- 06
Configuration & Performance Review
Connector and thread pool tuning, JVM heap and garbage collection, session handling, TLS settings and logging, reviewed against your real traffic rather than a template.
Why AceMQ
What you get that you don't get elsewhere
Named Engineers, Zero Cold Start
The same senior engineers stay on your account. They know your connectors, your JVM flags and which applications share a container, so a P1 call starts with a hypothesis rather than an interview.
No Help-Desk Layer
You reach a senior engineer directly by phone, email or Slack. No help desk collecting details to relay, and no escalation approval between you and someone who can read a thread dump and act on it.
Tomcat and Java, One Contract
Most Tomcat incidents are really JVM, class loader or driver problems. One team owns the server and the runtime under it, so nobody sends you back to the other vendor.
Patches Without a Forced Migration
Applications pinned to Java EE 8 or an old JDK can stay put and stay patched while the Jakarta migration is scheduled. The upgrade happens when your release calendar allows, not on Apache's.
Genuine Follow-the-Sun Coverage
Engineers across 26+ countries and every time zone. Your 3am heap-exhaustion alert is someone's mid-afternoon, with no overnight skeleton crew.
Full-Stack, Not Just the Servlet Container
We diagnose across the reverse proxy, the connector, the JVM, the connection pool and the database behind it. A surprising number of Tomcat incidents start one layer above or below it.
We support Apache Tomcat wherever it's deployed
Cloud, Kubernetes, bare metal, hybrid, and air-gapped — including environments where you can't give us outbound network access.
- Standalone Tomcat 8.5, 9, 10.1 and 11
- Tomcat embedded in Spring Boot applications
- Docker and Kubernetes
- OpenShift
- Behind Apache httpd, NGINX or a load balancer
- AWS, Azure and Google Cloud virtual machines
- On-premises servers
- Air-gapped / no outbound access
- Hybrid cloud
Version coverage
Tomcat versions AceMQ supports and patches
Apache supports Tomcat 11.0, 10.1 and 9.0 today, and 9.0.x support ends on 31 March 2027. AceMQ supports every line below 24/7, delivers patched builds for the lines Apache has stopped fixing, and plans the move to a supported release.
| Tomcat version | Minimum Java | Apache support | AceMQ coverage |
|---|---|---|---|
| Tomcat 11.0 | 17 | Supported, no end date announced | 24/7 support |
| Tomcat 10.1 | 11 | Supported, no end date announced | 24/7 support |
| Tomcat 9.0 | 8 | Ends 31 March 2027 | 24/7 support, and patched builds once Apache stops |
| Tomcat 9.1 (new branch) | Not yet published | Releases planned until 31 December 2030 | 24/7 support from its first release |
| Tomcat 10.0 | 8 | Ended 31 October 2022 | 24/7 support and patched builds |
| Tomcat 8.5 | 7 | Ended 31 March 2024 | 24/7 support and patched builds |
Source: tomcat.apache.org (Which version do I want? and the 11 February 2026 end of support notice for 9.0.x), checked 20 October 2026. The 9.1.x branch is announced but not yet released. Patched builds are delivered by AceMQ; Spring patches are not covered, and OSSeva (osseva.io) handles those.
Escalation Path
Your first hour of an Apache Tomcat outage
Every tier reaches a senior Apache Tomcat engineer. There is no tier-1 triage layer to get through.
- 15 minfirst responseEmergencyProduction down, messages not flowing, queue manager failure
- 1 hourfirst responseCriticalSevere degradation, high error rates, approaching capacity
- 4 hoursfirst responseHighPerformance issues, configuration problems, non-critical failures
- Next Dayfirst responseStandardQuestions, guidance, best practices, non-urgent improvements
P1 escalation path
A replay of one P1, from the first page to the written root-cause analysis
T+Elapsed15:00
15-minute P1 response, 24/7.
A response time, not a resolution time.
- T+00:00Paged
P1 opened, on-call engineer paged
Phone, email or Slack reaches the on-call senior engineer directly, whether the incident is in RabbitMQ, Kafka, Redis, PostgreSQL or Kubernetes. No web form, no tier-1 queue.
- T+15:00Live
Senior engineer on your bridge
A senior engineer who already knows your environment joins a live bridge, so nobody has to re-explain your topology.
- T+30:00If needed
Specialists across the stack join
When an incident crosses components, the engineers who know each one join. For RabbitMQ, the path runs to the core team.
- AfterEvery P1
Written root-cause analysis
Root cause, the fix applied and the prevention steps, delivered after every P1.
Support options
Four stages of Apache Tomcat support.
AceMQ offers Apache Tomcat support in four stages, each handing more of the day-to-day work to AceMQ: 24/7 support and emergency response for servers your team runs, proactive monitoring that finds thread, heap and connector problems first, managed Tomcat on your own infrastructure, and fully managed Tomcat on AceMQ infrastructure. Tomcat 8.5 to 11 is covered, and patched builds are available for versions Apache no longer fixes.
- Stage 1
Apache Tomcat 24/7 Support & Incident Management
You run it, we back you up
- 15-minute P1 response, 24/7, by phone, email or Slack
- Named senior engineers for Tomcat and the Java runtime under it
- Written root-cause analysis after every P1
Best for: Teams that run Tomcat themselves and need senior cover when a server misbehaves at 3am.
- Stage 2
Apache Tomcat 24/7 Support with Proactive Monitoring
You run it, we watch it with you
- Scheduled reviews of threads, heap, garbage collection and connector settings
- CVE alerts and patch planning for your exact Tomcat and Java versions
- Upgrade planning for Java 8 to 21 and Tomcat 9 to 10.1 or 11
Best for: Teams that want the leaking class loader or the exposed connector found in a review, not in an outage.
- Stage 3
Managed Apache Tomcat on Your Infrastructure
We run it in your cloud or data centre
- AceMQ holds the pager for your Tomcat servers
- Patching and Java upgrades staged to avoid downtime
- Runs on virtual machines, Kubernetes, OpenShift or air-gapped sites
Best for: Regulated estates that must keep application servers inside their own boundary.
- Stage 4
Fully Managed Apache Tomcat on AceMQ Infrastructure
We host it and run it, as a service
- Hosted and operated by AceMQ
- Patching, monitoring and backups included
- Java and Tomcat upgrades run for you
Best for: Teams that want Tomcat without an application-server rota.
| Who does what | Stage 1 24/7 support | Stage 2 Proactive monitoring | Stage 3 Managed, your infrastructure | Stage 4 Fully managed by AceMQ |
|---|---|---|---|---|
| Who runs Apache Tomcat day to day? | Your team | Your team, with AceMQ reviews | AceMQ | AceMQ |
| Where does it run? | Your infrastructure | Your infrastructure | Your cloud account or data centre | AceMQ infrastructure |
| 24/7 incident response | 15-minute P1 response | 15-minute P1 response | 15-minute P1 response | 15-minute P1 response |
| Health checks and CVE alerts | On request | Scheduled | Included | Included |
| Patching and upgrades | Your team, AceMQ advises | Planned with AceMQ | Done by AceMQ | Done by AceMQ |
| Monitoring and on-call | Your team | Your team | AceMQ | AceMQ |
| Data, keys and accounts | Yours | Yours | Yours | Your data, hosted by AceMQ |
Every Stage can start as an ad hoc engagement or an annual partnership, and you can move up or down a Stage as your team changes.
One partner for Apache Tomcat
Everything else AceMQ does for Apache Tomcat.
Support is one part of what AceMQ does for Apache Tomcat. The same engineers deliver consulting, health checks, migrations and end-of-life cover, and support the systems that usually run next to it.
- LifecycleEnd-of-life software support
- Enterprise supportOpen source support across your whole stack
- GuideApache Tomcat guide
Support for the rest of your stack
Messaging & Streaming
- RabbitMQ supportMessaging & Streaming
- Apache Kafka supportMessaging & Streaming
- IBM MQ supportMessaging & Streaming
- ActiveMQ supportMessaging & Streaming
- Azure Service Bus supportMessaging & Streaming
- Amazon SQS supportMessaging & Streaming
- Google Cloud Pub/Sub supportMessaging & Streaming
- Redpanda supportMessaging & Streaming
- Apache Pulsar supportMessaging & Streaming
- Message Queuing supportMessaging & Streaming
Databases & Caching
Search & Analytics
Lakehouse & Compute
Observability & Monitoring
Data Integration
Cloud & Containers
API Management
See support for all 52 technologiesShow fewer
Related services
What version of Java is compatible with Tomcat 9?
Tomcat 9.0.x runs on Java 8 and later, according to Apache's version table, so it runs on the current long-term-support releases such as Java 11, 17 and 21. Tomcat 10.1 needs Java 11 or later, and Tomcat 11.0 needs Java 17 or later. Moving to a newer Java usually comes first, because Tomcat 9 can take the new JDK without any change to the application namespace; the move to Tomcat 10.1 or 11 is the one that renames javax.* to jakarta.*.
Does anyone still use Tomcat?
Yes. Apache still releases Tomcat 9, 10.1 and 11, and Tomcat 11 is the current focus of development. Tomcat is also the default embedded web server in Spring Boot, so many Spring Boot applications run it without anyone installing it. Tomcat 9 stays common because it is the last version on Java EE 8, and moving to 10.1 or 11 means migrating the application to Jakarta EE.
When is Tomcat 9 EOL?
Apache announced on 11 February 2026 that support for Tomcat 9.0.x ends on 31 March 2027, which makes that the Tomcat 9 EOL date for the 9.0.x line. After that date, 9.0.x releases are highly unlikely, bugs that affect only 9.0.x will not be fixed, and security reports will not be checked against it. A new 9.1.x branch starts shortly before then and is planned to receive releases until 31 December 2030. AceMQ supports 9.0 24/7 now, will support 9.1 from its first release, and delivers patched 9.0 builds after Apache stops.
What does AceMQ's Tomcat enterprise support include?
Tomcat support covers 24/7 emergency incident response with a 15-minute P1 response, root cause analysis on every P1, CVE and patch advisory, patched builds for versions Apache no longer fixes, configuration and performance review, and Java and Tomcat upgrade planning. Every ticket goes to a named senior engineer assigned to your account, with no help-desk layer and no per-incident charge.
Can you patch Tomcat after Apache stops supporting it?
Yes. AceMQ delivers patched builds of Tomcat 8.5.x and 10.0.x today, and will deliver them for 9.0.x after Apache support ends on 31 March 2027. We backport each Apache Tomcat patch for a CVE from the supported branches into the line you run and ship signed builds as Docker images, packages or zip archives, so the application and its Java version stay as they are. The patches close the vulnerability gap; the Tomcat commercial support contract is what answers the phone when it breaks.
Can you help us move from Java 8 to Java 21?
Yes. Java upgrades go through the long-term-support releases in sequence, 8 to 11, 17 and 21, and each step is tested rather than skipped. Tomcat 9 runs on all of them, so the Java move and the Tomcat move can be separate projects. We inventory the JVM flags that no longer exist, libraries that need newer versions, TLS and module-access changes, and rehearse each step on a restored copy of production before the cutover. We do not give Oracle Java licensing advice.
Do you support Tomcat embedded in Spring Boot?
Yes, we support Tomcat as the container, including the embedded one inside a Spring Boot fat JAR. Spring Framework and Spring Boot patches are not part of this offer; for those, see OSSeva at osseva.io. Because an embedded Tomcat is a dependency, upgrading it often means a Spring Boot upgrade too, and we will tell you when that is the case.
How fast do you respond to a Tomcat production outage?
P1 emergencies, such as the server down, requests hanging or health checks failing, get a 15-minute first response with a senior engineer joining a live bridge. P2 critical issues are 1 hour, P3 high-priority 4 hours, and P4 standard questions next business day. These are contractual response times that apply nights, weekends and holidays.
What is the difference between Tomcat support and managed Tomcat?
Support means your team still runs Tomcat and has senior engineers to escalate to: an incident, a patch decision, a design question. Managed services means AceMQ also does the operational work on a schedule, on your infrastructure or ours. Most teams start with support, with 24/7 cover and proactive reviews, and add managed operations later if they want it.
Can we work with AceMQ on Apache Tomcat without a long contract?
Yes. AceMQ works on Apache Tomcat in two ways: ad hoc engagements for a defined piece of work, such as a health check, an upgrade or an incident, or an annual partner engagement that covers 24/7 support, proactive reviews and named engineers. Many teams start ad hoc and move to an annual partnership once the first engagement is done.
How much does AceMQ Apache Tomcat support or consulting cost?
Every AceMQ proposal is tailored to your requirements: your Apache Tomcat environment, the SLA you need, the hours of cover and the scope of work. We do not send generic quotes or publish a price list, because two estates of the same size rarely need the same thing. Request a quote and AceMQ replies within 1 hour.
Let's talk
Tomcat 9 Support Ends on 31 March 2027. Plan It Now.
Reactive cover, proactive reviews, or AceMQ running Apache Tomcat for you on your infrastructure or ours. A senior engineer scopes it with you, and quote requests are answered within 1 hour.
A senior Apache Tomcat engineer, not a sales queueQuote requests answered within 1 hourAd hoc engagements or an annual partnership
Production incident right now?Email an Apache Tomcat Architect
Get in Touch
Talk to an Apache Tomcat Expert
Send us a message and we'll follow up within one business day — or book a free 30-min consultation directly.
305-204-2607info@acemq.com66 W. Flagler St. 9th Floor
Miami, FL 33130
Miami, FL 33130
Prefer to talk now? Call us directly or use the consultation tab to find a time that works.