Apache Tomcat support, 24/7

24/7 Apache Tomcat Support with Emergency Response and Patches

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.

Support quotes answered within 1 hour, by a senior engineer.

160+
Customers supported
10+
Years in production support
40+
Sev 1 incidents handled a year
24/7
Americas, EMEA and APAC
1hour
Quote reply

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

Incident Triage

Tomcat problems we fix every week

Hung requests, redeploy leaks and balancer resets account for most Tomcat calls. Each row begins with a thread dump, connector setting or log line.

Common Apache Tomcat production problems and how AceMQ resolves them
Symptom you're seeingWhat we check firstTypical resolution
Requests hang and time out while CPU is idleA thread dump (jstack or jcmd Thread.print): are all connector threads parked, and on what? maxThreads against the blocked framesFix the pool or timeout the threads wait on, then the blocking call
OutOfMemoryError for Metaspace or heap after redeploysHeap histograms and a heap dump across redeploys; the undeploy log's memory-leak warnings; ThreadLocals, JDBC drivers on a shared class loader, threads never stoppedApplication 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 limitClose leaked connections in code, then size the pool
Intermittent 502 or connection reset behind a load balancerConnector keepAliveTimeout and connectionTimeout against the balancer's idle timeout; forwarded-header handling with RemoteIpValveAlign timeouts so Tomcat does not close idle connections first
ClassNotFoundException: javax.servlet or NoClassDefFoundError: jakarta.servlet after an upgradeTomcat 10 and later use jakarta.; Tomcat 9 uses javax.; scan the WAR and its librariesConvert with the Tomcat migration tool for Jakarta EE or move to Jakarta builds of dependencies
TLS handshake failures after a Java upgradejdk.tls.disabledAlgorithms against the connector's SSLHostConfig and what clients offerConnector TLS settings or a client update
A scanner flags the Tomcat version or the AJP connectorWhich 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 startupContainer limit against heap plus Metaspace, thread stacks and direct buffers; JAR scanning at startupJVM 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.

Tomcat hung while the CPU sits idle? Request a quote and an engineer replies within one hour.

Contact Us

Deployment coverage

Which Tomcat deployments does AceMQ support, and who covers what?

DeploymentWhat AceMQ coversWhat the vendor coversExcluded
Standalone Tomcat 8.5, 9, 10.1 and 1124/7 incident response, written RCA on P1s, connector, thread pool, JVM and TLS review, CVE advice and patches, upgradesThe Apache project publishes releases and states which versions are stable (tomcat.apache.org/whichversion.html, read 17 Nov 2026); it offers no response commitmentYour application code is reviewed, not rewritten
Tomcat embedded in Spring BootThe Tomcat container inside the fat JARSpring and VMware Tanzu support SpringSpring Framework and Spring Boot patches (see OSSeva at osseva.io)
Docker, Kubernetes and OpenShiftContainer memory against JVM memory, probes, graceful shutdown, session handlingThe platform vendor supports the platformControl-plane faults
Behind Apache httpd, NGINX or a load balancerTimeout alignment, forwarded headers, AJP exposureThe proxy vendor supports the proxyProxy faults
Java runtime under TomcatJVM flags, GC, TLS defaults, Java 8 to 21 upgrade stepsThe JDK vendor supports the JDKOracle Java licensing advice
Air-gapped serversSupport through your approved remote-access pathNoneAnything needing outbound access we are not given

Support options

Who provides enterprise support for Apache Tomcat? Vendor and independent support compared

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.

Vendor-shipped Tomcat (for example a Linux or middleware vendor) / Apache project
AceMQ independent support
What it coversVendor-shipped Tomcat (for example a Linux or middleware vendor): The vendor's own build, under its subscriptionApache project: Apache Tomcat releases and documentation
What it coversApache Tomcat 8.5, 9, 10.1 and 11, standalone or embedded, and the Java runtime under it
Hours and responseVendor-shipped Tomcat (for example a Linux or middleware vendor): Per vendorApache project: None stated
Hours and response24/7 across Americas, EMEA and APAC; targets from 15 minutes, by plan
Incidents (hangs, leaks, pools, TLS)Vendor-shipped Tomcat (for example a Linux or middleware vendor): Within plan scopeApache project: Community mailing lists
Incidents (hangs, leaks, pools, TLS)Core of our work, using thread dumps and heap dumps from your server
CVE fixesVendor-shipped Tomcat (for example a Linux or middleware vendor): Vendor's buildApache project: In the project's supported lines
CVE fixesPatch advice for your exact version and connector set-up, and tested patches for the line you run
PriceVendor-shipped Tomcat (for example a Linux or middleware vendor): Vendor subscriptionApache project: Free
Price$24,000 to $72,000 a year (USD), set by SLA, scope and deployment. Quote reply within 1 hour

What's Included

Everything in your Apache Tomcat support contract

Connectors, class loaders, TLS, Tomcat embedded in Spring Boot and the Java runtime underneath, all supported as one system.

  • 01

    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.

  • 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

Why Tomcat teams keep us on call

  • 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

    Round-the-clock coverage for customers in 26+ countries. 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.

Tomcat setups we cover

Standalone Tomcat 8.5 through 11, embedded Tomcat, containers on Kubernetes or OpenShift, and servers behind httpd, NGINX or a load balancer.

  • 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 we support

AceMQ supports every Tomcat line below. The table shows what Apache lists for each.

Tomcat versions we support
Tomcat versionMinimum JavaNamespace and specificationWhat Apache lists (tomcat.apache.org/whichversion.html, read 17 Nov 2026)What AceMQ does on it
11.017jakarta.*, Servlet 6.1 (Jakarta EE 11)Stable, current development focus (11.0.29)24/7 support
10.111jakarta.*, Servlet 6.0 (Jakarta EE 10)Stable (10.1.61)24/7 support
9.08javax.*, 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 branch24/7 support and patches for the line you run
8.57javax.*Listed as archived (8.5.100)24/7 support and an upgrade plan
10.08jakarta.*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

The Tomcat to Jakarta migration, in the order that works

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

Tomcat consulting and professional services

Tomcat consulting and professional services
DeliverableWhat you receive
Server health checkConnector, thread pool, JVM, GC, session handling, TLS and logging reviewed against your traffic, and a ranked fix list
CVE exposure reviewCVEs 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 planJava 8 to 21 steps, Tomcat 9 to 10.1 or 11, the namespace migration, rehearsal and rollback
Container sizingHeap against container limit, Metaspace, thread stacks and direct buffers, probe and shutdown settings
Platform migration assessmentA written inventory of an application server estate and a mapping to Tomcat or another target
RunbooksThread dump and heap dump capture, leak triage, certificate rotation

Escalation Path

Your first hour of an Apache Tomcat outage

Whoever takes a hung application takes a thread dump first, and knows what maxThreads and parked connector threads imply.

  1. From 15 min (by plan)first responseEmergencyProduction application unreachable, all connector threads blocked, Tomcat failing to start after a change
  2. 1 hourfirst responseCriticalMetaspace or heap exhaustion after redeploys, 502s behind the load balancer, container killed for memory
  3. 4 hoursfirst responseHighTLS handshake failures after a Java update, AJP connector flagged by a scanner, slow startup from JAR scanning
  4. Next Dayfirst responseStandardQuestions on connector tuning, javax to jakarta moves, valve configuration and version upgrades

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.

Need a named Tomcat engineer for your applications? Ask for a quote or contact us.

Contact Us

Pricing

What does AceMQ Apache Tomcat support cost?

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

Four tiers of Apache Tomcat support.

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.

  • Tier 1

    Apache Tomcat 24/7 Support & Incident Management

    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.

  • Tier 2

    Apache Tomcat 24/7 Support with Proactive Monitoring

    We tune connectors and review deployments

    Best for: Teams whose redeploys leak memory or whose keepAliveTimeout never matched the balancer.

  • Tier 3

    Managed Apache Tomcat on Your Infrastructure

    We operate Tomcat servers you own

    Best for: Organizations that need patching and monitoring done on their own hosts or clusters.

  • Tier 4

    Fully Managed Apache Tomcat on AceMQ Infrastructure

    We run your Tomcat servers and deployments

    Best for: Teams who want applications served without owning servlet container operations.

FAQ

Apache Tomcat support questions

Still have questions about Apache Tomcat? Email an Expert

Who provides enterprise support for Apache Tomcat?

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.

What does 24/7 Tomcat support cover with AceMQ?

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.

What version of Java is compatible with Tomcat 9?

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.

Does anyone still use Tomcat?

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.

Why do my Tomcat requests hang while the CPU is idle?

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.

Why does Tomcat run out of Metaspace after redeploys?

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.

Can you help us move from Java 8 to Java 21?

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.

Can you move us from Tomcat 9 to 10.1 or 11?

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.

Do you support Tomcat embedded in Spring Boot?

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.

What does a Tomcat health check include?

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.

Who offers Tomcat consulting and professional services?

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.

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.

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 we hire Tomcat help for a single job?

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.

How much does a Tomcat support contract cost?

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

Take the Thread Dump Before the Next Hang

Send us your Tomcat and Java versions and whether it runs standalone or inside Spring Boot. We reply to quote requests 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