Apache Tomcat Support
Tomcat runs a lot of business software, and most of the time nobody thinks about it. Then a security scan flags it, a version runs out of support, or it stops answering at two in the morning. We've worked with Tomcat for over 20 years, and we help DevOps teams and system administrators with the Tomcat side of things, as an extra set of hands or a second set of eyes, so the people who already know your systems don't have to become Tomcat specialists on top of everything else.
Who this is for
You've got Tomcat in production, and it's one of fifty things your team is responsible for. You know your applications and your infrastructure better than anyone. What you may not have is the time to dig into a Tomcat upgrade, untangle a connector configuration somebody set up years ago, or read through thread dumps while the phones are ringing.
That's where we come in. We're not here to take over your environment. We work alongside your team, inside your change process, and we leave behind notes your people can use the next time.
Upgrades
Tomcat 8.5 stopped getting security fixes in March 2024, and Apache has announced that support for Tomcat 9.0.x ends on March 31, 2027. Tomcat 9 itself carries on in a new 9.1.x line that will keep getting support, but getting there from 9.0.x is still an upgrade to plan and test. If you're on 8.5 or 9.0.x, an upgrade is coming whether it's on the calendar or not.
Moving to Tomcat 10.1 or 11 instead is more than swapping out a directory. Those versions switched from the javax.* package names to jakarta.*, so your applications, the libraries they use, and parts of your configuration all have to follow. Newer versions also need a newer Java. We work out what in your stack has to change, use Apache's migration tooling where it fits, fix by hand what it can't, and test it with you before anything gets near production.
Security hardening
- Removing the example and default applications that ship with Tomcat
- Locking down or removing the Manager and Host Manager apps
- Closing or securing the AJP connector, the door the "Ghostcat" attack (CVE-2020-1938) walked through
- TLS configuration, whether Tomcat handles it or a proxy in front of it does
- Running Tomcat as its own user with tight file permissions, and keeping version details out of error pages
- A patching routine, so you're never three years behind again
If a vulnerability scan or an audit has handed you a list of Tomcat findings, we can work through it with you and tell you which ones matter.
Performance and stability
- JVM heap and garbage collection settings matched to your actual workload
- Connector thread pools, timeouts and keep-alive settings
- Database connection pools: exhaustion, leaks and stale connections
- Memory that climbs after every redeploy until something falls over
- Reading thread dumps, heap dumps and logs to find what's actually stuck
When it's down
If Tomcat is down or limping, get in touch and tell us what you're seeing. We'll help you work out what's wrong and get it running again, then help find the cause so it doesn't happen next week. We're a small company, not a round-the-clock call center, but after-hours help is available. It can be part of a monthly support package, or arranged as a one-time thing, say for a weekend upgrade or a maintenance window in the middle of the night.
Around Tomcat
Tomcat rarely runs alone, and problems don't always start in Tomcat. We also work with what sits next to it: Apache httpd or nginx in front, load balancing and session handling across several instances, the Linux server underneath, and moving the whole setup to a new server or host. If your Tomcat configuration lives in scripts, configuration management or container images, that's where we'll make our changes, so they stick.
Tomcat inside something you bought
Plenty of commercial products ship with their own copy of Tomcat tucked inside. When the vendor is slow to update it, or isn't around anymore, you're left running an old Tomcat you never chose. We can often update or harden the bundled copy without breaking the product, and we'll tell you plainly when it's too risky to try.
How we work
Work is done remotely, over Zoom when it helps to look at something together and over SSH when it's quicker for us to dig in directly. You'll work with the same person who does the work, here in the United States, and we follow your access rules, tickets and change windows. When we're done, you get a written summary of what changed and why.
- By the task: a defined job, such as an upgrade or a hardening pass, quoted up front
- By the hour: help with a specific problem, with no commitment
- Monthly: a support package with someone to call for your Tomcat environments, including after hours if you need it, at a predictable cost
A good fit if
- You run Tomcat in production and want backup for it
- An upgrade or the move to jakarta has been put off
- A scan or an audit flagged your Tomcat setup
Probably not a fit if
- You need a staffed operations center around the clock
- You're after a full-time, on-site Java developer
Common questions
Will you work with our team, or instead of it?
With it. Most of the time we're backing up people who already run the environment. We explain what we find and what we change, so your team isn't left depending on us.
Do you need full access to our servers?
Only as much as the job needs, for as long as it needs it. Some work can be done entirely over a screen share with your people at the keyboard. When we do need access, it's for us alone, and you can shut it off when we're finished.
Can you help with the application code too?
Yes. The jakarta move in particular often means changes to the application itself, not just Tomcat. That's work we do, and for bigger jobs it fits with our Custom Software Projects.
What about the servers Tomcat runs on?
We look after those as well. See Linux Server Administration.
Tell us which Tomcat and Java versions you're running, what's in front of them, and what you need: an upgrade, a fix, or someone to call.
Get Tomcat help