Tomcat Consulting & Support

Tomcat Consulting for Jakarta Migrations, Upgrades and Tuning

Tomcat consulting from AceMQ covers configuration reviews, Java and Tomcat upgrades, the javax to jakarta migration from Tomcat 9 to 10.1 or 11, and container sizing, led by senior engineers who also staff the 24/7 Tomcat support rota. Apache ends support for Tomcat 9.0.x on 31 March 2027, so many projects start there. Engagements are quoted per engagement.

A senior engineer, not an SDR. No sales sequence attached.

Fastest response target, by plan
15 min
On-call cover
24/7
AceMQ customers
160+
Years in business
10+

Without rewriting an application that already worksFor production incident cover, see AceMQ Apache Tomcat 24/7 support.

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

The Problem

Why teams call us about Apache Tomcat

Eight Tomcat problems an AceMQ review starts from, from hanging requests to a namespace change. If one describes your week, that is where the review starts.

  1. 01

    Requests hang and time out while CPU is idle

  2. 02

    Metaspace or heap grows after every redeploy until the node restarts

  3. 03

    Tomcat 9 applications must move to the jakarta namespace and nobody knows which libraries block it

  4. 04

    Intermittent 502 or connection resets behind a load balancer

  5. 05

    Pool errors such as "Timeout waiting for idle object" under load

  6. 06

    A container is killed for memory while the heap graph looks healthy

  7. 07

    A scanner flags the Tomcat version or the AJP connector

  8. 08

    Logins are lost when a node restarts because sessions are not replicated or stored anywhere

A good fit if Tomcat serves production traffic and you want one team that reads your thread dumps, plans the Jakarta move and answers at night.

Not a fit for small teams with non-critical workloads. AceMQ is not a budget consultancy: we work with enterprises running business-critical and compliance-heavy Apache Tomcat.

Running Apache Tomcat in production? Get a quote from a senior engineer, answered within one hour.

Contact Us

How it breaks, and the fix

What happens to every application when one slow call uses up Tomcat's request threads?

Tomcat serves every web application in a connector from one pool of request threads, 200 by default on the HTTP connector, with a queue of 100 waiting connections. An application whose requests wait on a slow database call holds its threads, so the pool fills, and then the other applications wait behind it while their own code is idle.

One slow call, one shared thread pool

Clients, Tomcat and three web applications

Illustrative
  1. Requests finish quickly, busy threads stay well below maxThreads and nothing waits in the accept queue.

  2. The reports application holds its threads on a slow database call. Every thread is busy, new connections queue, and clients of the orders and login applications see timeouts while that code sits idle.

  3. The slow call gets its own timeout, the database pool is sized from measured concurrency, and the thread pool no longer fills, so the reports application fails on its own and the others carry on.

A thread dump (jstack or jcmd with Thread.print) shows it in minutes: count the request threads and read what the blocked frames wait on. If most wait in the same pool borrow or socket read, the fix is a timeout on that call and a pool sized to the database, not a larger maxThreads. Where one application should not be able to starve the others, it moves to its own connector or its own Tomcat.

Our Services

Apache Tomcat Consulting & Services

AceMQ runs five Tomcat service lines: health check, Jakarta migration, Java and Tomcat upgrade planning, container sizing, and session and availability design. A senior engineer leads each one, and any of them can roll into 24/7 support.

  • 01

    Tomcat Health Check

    The fixed-scope entry engagement: a written report on how your Tomcat is configured and where it is exposed, which your team can act on with or without AceMQ.

    • Connector, thread pool and timeout settings
    • JVM heap, Metaspace and garbage collection
    • TLS, sessions, logging and the AJP connector
    • CVEs that apply to your exact version
  • 02

    Jakarta Migration

    Moving Tomcat 9 applications to 10.1 or 11, where the namespace changes from javax to jakarta, rehearsed before it touches live traffic.

    • Scan of the WAR and its libraries for javax references
    • First conversion with Apache's migration tool for Jakarta EE
    • Libraries replaced with Jakarta builds
    • Cutover with the old Tomcat as the rollback
  • 03

    Java and Tomcat Upgrade Planning

    A written path across Java 8, 11, 17 and 21 and across Tomcat lines, tested one step at a time.

    • Version path per application
    • Tomcat 9 on current long-term-support Java as a separate step
    • Rehearsal on a restored copy
    • Rollback for each step
  • 04

    Container and Kubernetes Sizing

    Heap, Metaspace, thread stacks and direct buffers sized against the container limit, with probes and graceful shutdown set to match.

    • Container limit against JVM memory
    • Startup and JAR scanning time
    • Readiness and shutdown behavior
    • Session handling when pods move
  • 05

    Session and Availability Design

    How sessions survive a node restart or a failover: sticky sessions, replication or an external store, chosen from your traffic.

    • Session options compared for your applications
    • Load balancer and keep-alive timeout alignment
    • Failover drill with clients connected
    • Runbook for node replacement
  • Response targets from 15 minutes, by plan

    24/7 Apache Tomcat Support

    Named senior engineers on your account — response targets from 15 minutes, by plan, no ticket routing.

    • Response targets from 15 minutes, by plan
    • Named engineer, zero cold-start
    • Proactive CVE & health monitoring
    • Quarterly deployment reviews

Want AceMQ to take this off your team's plate? Tell us about your Apache Tomcat estate.

Contact Us

24/7 Support

Apache Tomcat Support When It Matters Most

AceMQ Tomcat support gives you an AceMQ engineer and response targets from 15 minutes, by plan, when production is failing, 24/7, with the Java runtime under it.

  1. From 15 min (by plan)first responseEmergencyProduction down, messages not flowing, queue manager failure
  2. 1 hourfirst responseCriticalSevere degradation, high error rates, approaching capacity
  3. 4 hoursfirst responseHighPerformance issues, configuration problems, non-critical failures
  4. Next Dayfirst responseStandardQuestions, guidance, best practices, non-urgent improvements

Response targets by plan; your contract sets the tier.

P1 escalation path

A replay of one P1, from the first page to the written root-cause analysis

SLA 15:00
T+Elapsed15:00
Engineer on your bridge

Response targets from 15 minutes, by plan; 24/7.
A response time, not a resolution time.

  1. T+00:00

    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.

    Paged
  2. T+15:00

    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.

    Live
  3. T+30:00

    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.

    If needed
  4. After

    Written root-cause analysis

    Root cause, the fix applied and the prevention steps, delivered after every P1.

    Every P1

How Our Support Actually Works

Beyond SLAs — the model behind senior-only, zero-cold-start expert access.

  • Named Engineers on Your Account

    Every ticket is handled by a senior SME assigned to your account — not a pool of anonymous agents. Zero cold-start. No re-explaining your environment.

  • Live Escalation on Any Ticket

    Any ticket can be escalated to a live session with your named engineer via calendar booking. No gatekeeping, no approval required — direct access, always.

  • Proactive Risk Mitigation

    Quarterly health checks on your deployment plus shared intelligence from our support customers — we surface risks before they reach production.

  • Critical Bug & CVE Intelligence

    Proactive alerts on critical bugs and CVEs affecting your exact version, with version compliance monitoring so you're never caught off guard.

How It Works

What actually happens next

An AceMQ Tomcat engagement runs in four stages: a scoping call with a quote within 1 hour, a review, a written plan, then the work or a handover. Each stage ends in writing.

Quote within 1 hour

Scoping call and quote

A senior AceMQ engineer asks what you run: the Tomcat and Java versions, standalone or embedded in Spring Boot, container or virtual machine, the proxy in front, and what has prompted the question. A quote request is answered within 1 hour.

Scoped per estate

Review

Connector and thread pool settings, JVM and garbage collection, class loader leak signs, TLS, session handling, logging and the CVEs that apply to your exact version, read from your real configuration and thread and heap dumps. Findings are written down and your team keeps them.

Scoped per estate

Written plan

A recommendation in writing: the Java and Tomcat path in the order your applications can take it, the namespace conversion where it applies, and a rehearsal on a restored copy of production with the old server kept as the rollback.

Ongoing or fixed scope

Run the work or hand over

Changes staged one node at a time, each with a rollback. The work ends with runbooks for thread dump and heap dump capture, leak triage and certificate rotation. You can stop there, add 24/7 Tomcat support, or have AceMQ run the estate.

  • Written findings before any change
  • Changes staged and reversible, with a rollback plan
  • Your engineers in the room
  • Ad hoc engagements or an annual partnership

A senior engineer, not an SDR. No sales sequence attached.

Customer Success

Real Apache Tomcat Results

Typical Tomcat engagements, described as scopes. Each card links to the full write-up.

  • Consulting

    Tomcat 9 to 10.1 Jakarta Namespace Migration Plan

    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.

    Apache TomcatJavaDocker
  • Consulting

    Tomcat Connector and Thread Pool Review Behind a Load Balancer

    Engineering Organization

    A typical consulting engagement for Tomcat nodes that return intermittent 502 errors and hang under load: a review of connector timeouts, thread and connection pools and session handling, with a failover drill.

    Apache TomcatNGINXJava
All use cases

Solutions

Every way AceMQ works with Apache Tomcat.

AceMQ covers Apache Tomcat end to end. Projects: consulting and implementation, health checks and migrations. Ongoing cover in four tiers, from 24/7 support and incident management to proactive monitoring, managed Apache Tomcat on your infrastructure and fully managed Apache Tomcat on AceMQ infrastructure, plus end-of-life versions.

Projects

Build, fix or move Apache Tomcat

Fixed-scope work led by a senior engineer: architecture and new builds, a health check of what you run today, or a migration with a reversible cutover.

Side by side

Tomcat consulting, a support contract or both: what changes?

A consulting engagement fixes or changes something and ends with documents and runbooks. A support contract keeps an engineer on call for your Tomcat. Many teams start with consulting and add support once the upgrade path is clear.

Tomcat consulting and Tomcat support compared on purpose, duration, who works it, what you receive and how it is bought
QuestionTomcat consulting engagementTomcat 24/7 support contract
What is it for?A review, an upgrade, a Jakarta migration or a sizing exercise with a defined end.Incidents, patches and advice at any hour, for as long as the contract runs.
How long does it run?A fixed scope, scoped after the review.An annual contract.
Who works it?Senior AceMQ engineers who also staff the support rota.A named senior engineer on your account, reached directly by phone, email or Slack.
What do you receive?Written findings, a rehearsed plan, a rollback and runbooks.Response targets from 15 minutes, by plan, and a written root-cause analysis on every P1.
How is it bought?Quoted per engagement. Quote reply within 1 hour.$24,000 to $72,000 a year (USD), set by SLA, scope and deployment, as published on the Tomcat support page.

Support terms and versions are on the Tomcat end of life dates guide and the Tomcat support page.

Not sure which option fits? A senior Apache Tomcat engineer will scope it with you.

Contact Us

One partner, not five

We Support Your Entire Tech Stack

Apache Tomcat rarely fails in isolation. AceMQ covers the full surrounding infrastructure — so one team owns the whole path instead of pointing at each other.

See all the technologies we supportShow fewer

What is included

What a Tomcat consulting engagement includes, and what it does not

Each row names one area of work. The right column is what stays outside the engagement.

Tomcat consulting scope: what is included and what is not, by area
AreaIncludedNot included
ReviewConnector and thread pool settings, JVM and garbage collection, class loader leak signs, TLS, sessions, logging, applicable CVEs and a ranked fix listRewriting your application code
UpgradesJava 8 to 11, 17 and 21 steps, Tomcat 9 to 10.1 or 11, the javax to jakarta scan and conversion, rehearsal on a restored copy and a rollbackCode changes the conversion does not need; Spring Framework and Spring Boot patches
ContainersHeap, Metaspace, stacks and direct buffers against the container limit; probes and shutdown behaviorKubernetes control-plane faults
HandoverRunbooks for thread and heap dumps, leak triage and certificate rotation24/7 incident response, unless you add a support contract
Java licensingThe Java runtime's behavior and upgrade stepsOracle Java licensing advice

Pricing

How Tomcat consulting is priced

Tomcat consulting is quoted per engagement. A health check is a fixed scope; upgrade, migration and design work is scoped after the review so the quote matches the estate. A quote request is answered within 1 hour.

If you want 24/7 cover as well, the published range for AceMQ support is $24,000 to $72,000 a year (USD), set by SLA, scope and deployment. See Tomcat support.

Fit

Who Tomcat consulting from AceMQ is not for

  • You want someone to rewrite or re-platform the application itself.
  • You need an opinion on Oracle Java licensing; that stays with your agreement and counsel.
  • You run one small internal application, nothing is due to change and Apache's version table answers your question.

FAQs

Apache Tomcat Questions Answered

Answers on Tomcat consulting from AceMQ: what is included, how the Jakarta migration works, when Tomcat 9 support ends and which defaults a review starts from.

Still have questions about Apache Tomcat? Email an Expert

What does Tomcat consulting include?

A health check of connectors, thread pools, the JVM, TLS and sessions, upgrade and Jakarta migration planning, container sizing and availability design, each with written findings and a rollback plan. AceMQ reviews your application's behavior on Tomcat; it does not rewrite application code.

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, with the same engineers who work the 24/7 support rota.

How do you migrate from Tomcat 9 to Tomcat 10.1 or 11?

Tomcat 10 and later use the jakarta namespace where Tomcat 9 uses javax. We move Java first, scan the WAR and its libraries for javax references, convert with Apache's migration tool for Jakarta EE, replace libraries that have Jakarta builds, rehearse on a copy of production and cut over with the old server as the rollback.

When does Tomcat 9 support end?

Apache announced on 11 February 2026 that support for Tomcat 9.0.x ends on 31 March 2027. A 9.1.x branch is planned to receive releases until 31 December 2030. The Tomcat support page covers what AceMQ does for the line you run.

What are Tomcat's default thread and connection settings?

On the HTTP connector, Tomcat's 10.1 documentation lists maxThreads at 200, acceptCount at 100 and maxConnections at 8192 for the NIO connector. connectionTimeout defaults to 60000 ms, though the standard server.xml sets 20000 ms, and keepAliveTimeout follows connectionTimeout unless set. Those defaults are where a tuning review starts, not where it ends.

Do you tune Tomcat embedded in Spring Boot?

Yes, the Tomcat container inside the application. Spring Framework and Spring Boot patches are not part of this offer, and upgrading an embedded Tomcat often means a Spring Boot upgrade, which we say when it applies.

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. Most contracts run $24,000–72,000 a year, depending on the SLA, the scope and how Apache Tomcat is deployed, with aggressive discounts when several technologies share one contract. Request a quote and AceMQ replies within 1 hour.

Let's talk

Find What Holds Your Tomcat Threads

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 AceMQ engineer, not a sales queueAbout your Tomcat estate, not a pitch deckQuote requests answered within 1 hour

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 1 hour — or book a free 30-min consultation directly.

305-204-2607
info@acemq.com
66 W. Flagler St. 9th Floor
Miami, FL 33130

Prefer to talk now? Call us directly or use the consultation tab to find a time that works.

We respond within 1 hour.

Pick a time that works — no pressure, no pitch. Just 30 minutes with an expert.

We respond within 1 hour.