Emergency Incident Response
Server down, requests hanging, out of memory, or failing after a patch. With response targets from 15 minutes, by plan, a senior engineer joins a live bridge, 24/7, with access to diagnose, not a ticket acknowledgement.
Apache Tomcat support, 24/7
Last reviewed by Tyler Eastridge
AceMQ supports Apache Tomcat 24/7, standalone or embedded in Spring Boot, on Tomcat 8.5, 9, 10.1 and 11. Most calls start with one of three problems: requests hanging while CPU is idle because the thread pool is waiting on a database or downstream call, OutOfMemoryError after redeploys, or failures after the javax to jakarta namespace change.
24/7 across Americas, EMEA and APAC, with response targets from 15 minutes, by plan, and a written root cause analysis on every P1.
Customers




Partners


Incident Triage
Hung requests, redeploy leaks and balancer resets account for most Tomcat calls. Each row begins with a thread dump, connector setting or log line.
| Symptom you're seeing | What we check first | Typical resolution |
|---|---|---|
| Requests hang and time out while CPU is idle | A thread dump (jstack or jcmd Thread.print): are all connector threads parked, and on what? maxThreads against the blocked frames | Fix the pool or timeout the threads wait on, then the blocking call |
| OutOfMemoryError for Metaspace or heap after redeploys | Heap histograms and a heap dump across redeploys; the undeploy log's memory-leak warnings; ThreadLocals, JDBC drivers on a shared class loader, threads never stopped | Application fix, then clean redeploys or a restart policy |
| "Cannot get a connection, pool error Timeout waiting for idle object" | Pool size against load; abandoned-connection logging in a test run; pool maximum against the database's connection limit | Close leaked connections in code, then size the pool |
| Intermittent 502 or connection reset behind a load balancer | Connector keepAliveTimeout and connectionTimeout against the balancer's idle timeout; forwarded-header handling with RemoteIpValve | Align timeouts so Tomcat does not close idle connections first |
| ClassNotFoundException: javax.servlet or NoClassDefFoundError: jakarta.servlet after an upgrade | Tomcat 10 and later use jakarta.; Tomcat 9 uses javax.; scan the WAR and its libraries | Convert with the Tomcat migration tool for Jakarta EE or move to Jakarta builds of dependencies |
| TLS handshake failures after a Java upgrade | jdk.tls.disabledAlgorithms against the connector's SSLHostConfig and what clients offer | 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 set-up; AJP default hardening arrived in 9.0.31 after CVE-2020-1938 (Ghostcat) | Patch, or a configuration that removes the exposure |
| Container killed for memory, or slow startup | Container limit against heap plus Metaspace, thread stacks and direct buffers; JAR scanning at startup | JVM and container settings; skip scanning for libraries with no annotations or TLDs |
After each production incident we send an RCA that names the connector, class loader or runtime setting responsible and the fix applied.
Deployment coverage
| Deployment | What AceMQ covers | What the vendor covers | Excluded |
|---|---|---|---|
| Standalone Tomcat 8.5, 9, 10.1 and 11 | 24/7 incident response, written RCA on P1s, connector, thread pool, JVM and TLS review, CVE advice and patches, upgrades | The Apache project publishes releases and states which versions are stable (tomcat.apache.org/whichversion.html, read 17 Nov 2026); it offers no response commitment | Your application code is reviewed, not rewritten |
| Tomcat embedded in Spring Boot | The Tomcat container inside the fat JAR | Spring and VMware Tanzu support Spring | Spring Framework and Spring Boot patches (see OSSeva at osseva.io) |
| Docker, Kubernetes and OpenShift | Container memory against JVM memory, probes, graceful shutdown, session handling | The platform vendor supports the platform | Control-plane faults |
| Behind Apache httpd, NGINX or a load balancer | Timeout alignment, forwarded headers, AJP exposure | The proxy vendor supports the proxy | Proxy faults |
| Java runtime under Tomcat | JVM flags, GC, TLS defaults, Java 8 to 21 upgrade steps | The JDK vendor supports the JDK | Oracle Java licensing advice |
| Air-gapped servers | Support through your approved remote-access path | None | Anything needing outbound access we are not given |
Support options
Apache Tomcat is an open-source project from the Apache Software Foundation, and the project provides releases and community help rather than a support contract. Commercial support comes from Linux and middleware vendors that ship their own Tomcat builds, and from independent providers such as AceMQ for the Apache Tomcat you run.
What's Included
Connectors, class loaders, TLS, Tomcat embedded in Spring Boot and the Java runtime underneath, all supported as one system.
Server down, requests hanging, out of memory, or failing after a patch. With response targets from 15 minutes, by plan, a senior engineer joins a live bridge, 24/7, with access to diagnose, not a ticket acknowledgement.
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.
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.
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.
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.
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
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.
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.
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.
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.
Round-the-clock coverage for customers in 26+ countries. Your 3am heap-exhaustion alert is someone's mid-afternoon, with no overnight skeleton crew.
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.
Standalone Tomcat 8.5 through 11, embedded Tomcat, containers on Kubernetes or OpenShift, and servers behind httpd, NGINX or a load balancer.
Version coverage
AceMQ supports every Tomcat line below. The table shows what Apache lists for each.
| Tomcat version | Minimum Java | Namespace and specification | What Apache lists (tomcat.apache.org/whichversion.html, read 17 Nov 2026) | What AceMQ does on it |
|---|---|---|---|---|
| 11.0 | 17 | jakarta.*, Servlet 6.1 (Jakarta EE 11) | Stable, current development focus (11.0.29) | 24/7 support |
| 10.1 | 11 | jakarta.*, Servlet 6.0 (Jakarta EE 10) | Stable (10.1.61) | 24/7 support |
| 9.0 | 8 | javax.*, Servlet 4.0 (Java EE 8) | Stable (9.0.124); Apache has posted a notice about the future of the 9.0.x line and a 9.1.x branch | 24/7 support and patches for the line you run |
| 8.5 | 7 | javax.* | Listed as archived (8.5.100) | 24/7 support and an upgrade plan |
| 10.0 | 8 | jakarta.* | Listed as superseded (10.0.27) | 24/7 support and an upgrade plan to 10.1 or 11 |
Tomcat 9 runs on the current long-term-support Java releases, so the Java move and the Tomcat move can be separate projects. The move to 10.1 or 11 is the one that renames javax. to jakarta..
In practice
Move Java first. Tomcat 9 runs on Java 8 and later. Upgrade through 11, 17 and 21 in sequence and test each step.
Scan the namespace. Find every javax.servlet, javax.websocket and similar reference in the WAR and its libraries.
Convert or replace. Use the Tomcat migration tool for Jakarta EE for a first conversion, then replace libraries that have Jakarta builds.
Rehearse on a copy of production. Same thread pools, same TLS, same proxy.
Cut over with the old Tomcat as the rollback.
We do not give Oracle Java licensing advice; that stays with your agreement and counsel.
Consulting
| Deliverable | What you receive |
|---|---|
| Server health check | Connector, thread pool, JVM, GC, session handling, TLS and logging reviewed against your traffic, and a ranked fix list |
| CVE exposure review | CVEs applicable to your exact version and connector set-up, with the AJP connector reviewed, and a tested path to the fix |
| Java and Tomcat upgrade plan | Java 8 to 21 steps, Tomcat 9 to 10.1 or 11, the namespace migration, rehearsal and rollback |
| Container sizing | Heap against container limit, Metaspace, thread stacks and direct buffers, probe and shutdown settings |
| Platform migration assessment | A written inventory of an application server estate and a mapping to Tomcat or another target |
| Runbooks | Thread dump and heap dump capture, leak triage, certificate rotation |
Escalation Path
Whoever takes a hung application takes a thread dump first, and knows what maxThreads and parked connector threads imply.
Your plan sets the target. A cluster of hung connector threads on a live site and a question about RemoteIpValve do not share a clock.
Pricing
Tomcat support is quoted per scope and generally costs $24,000 to $72,000 a year. The number depends on how many instances and applications are in production, embedded or standalone use, and the response level.
Prices are in USD. Response targets start at 15 minutes depending on plan, 24/7, and quote requests are answered within 1 hour. Adding Java, Spring Boot or database support brings a multi-technology discount.
Support options
AceMQ offers Apache Tomcat support in four tiers, 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.
Your team runs Tomcat, we take escalations
Best for: Application teams who deploy WARs themselves and want an expert for hangs, leaks and balancer resets.
We tune connectors and review deployments
Best for: Teams whose redeploys leak memory or whose keepAliveTimeout never matched the balancer.
We operate Tomcat servers you own
Best for: Organizations that need patching and monitoring done on their own hosts or clusters.
We run your Tomcat servers and deployments
Best for: Teams who want applications served without owning servlet container operations.
One partner for Apache Tomcat
Tomcat work often involves Java runtime tuning, the Spring layer above it and the databases below.
The Apache project provides releases and community help, with no support contract. Linux and middleware vendors support the Tomcat builds they ship. Independent providers such as AceMQ support the Apache Tomcat you run, 24/7, with response targets from 15 minutes, by plan, together with the Java runtime under it.
Round-the-clock response from engineers who read Tomcat and Java diagnostics, starting within 15 minutes on the top plans. A Sev 1 example: requests hang while CPU is idle. We take thread dumps, find what the connector threads wait on, restore service, and send an RCA. P2 1 hour, P3 4 hours.
Apache's version table lists Java 8 as the minimum for Tomcat 9.0.x, so it runs on current long-term-support releases such as 11, 17 and 21. Tomcat 10.1 needs Java 11 or later and Tomcat 11 needs Java 17 or later.
Yes. Apache releases Tomcat 9, 10.1 and 11, and Tomcat is 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.
The request threads are usually parked waiting on a database pool, a slow downstream call or a lock. A thread dump shows which resource. We fix that resource, then the pool and timeout settings.
A hot redeploy leaves the old web application class loader pinned by a ThreadLocal, a JDBC driver registered on a shared loader or a thread the application never stopped. We compare heap dumps across redeploys to find the holder.
Yes. We go through the LTS releases in sequence, test each step, and rehearse on a restored copy of production. Tomcat 9 runs on all of them, so the Java move can stand alone.
Yes. The namespace change from javax. to jakarta. is the work. We scan, convert, rehearse and cut over with the old server as the rollback.
Yes, the Tomcat container. Spring Framework and Spring Boot patches are not part of this offer; see OSSeva at osseva.io. Upgrading an embedded Tomcat often means a Spring Boot upgrade, and we say when that is the case.
Connector and thread pool settings, JVM and GC, class loader leak signs, TLS, session handling, logging, applicable CVEs, and a ranked plan. Quotes are answered within 1 hour.
Linux and middleware vendors offer services around their own Tomcat builds, and independent firms such as AceMQ consult on Apache Tomcat and the Java runtime beneath it. One team owns the server and the JVM, so you are not sent back to the other vendor. See enterprise support.
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.
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.
Yes. A one-off engagement, such as a hang investigation, a TLS repair or a Tomcat 9 to 10.1 migration plan, needs no yearly agreement. The annual option gives 24/7 response and engineers who already know your connectors, which fits applications customers rely on daily.
Typical annual contracts are $24,000 to $72,000 (USD). The price reflects the number of Tomcat instances and applications in production, whether Tomcat is standalone or embedded in Spring Boot, the Java and Tomcat versions you run, and the response level. Request a quote and we reply within 1 hour.
Let's talk
Send us your Tomcat and Java versions and whether it runs standalone or inside Spring Boot. We reply to quote requests within 1 hour.
Production incident right now?Email an Apache Tomcat Architect