What our engineers handle on Java and Apache Tomcat
This is the hands-on work, done by a person: the jobs the automatic tools cannot do for you.
- 1Choose the Java version and tune heap, garbage collection and thread pools
- 2Configure Tomcat connectors, TLS, session handling and a reverse proxy in front
- 3Remove default webapps and tighten the manager and admin interfaces
- 4Set up deployments, log rotation and monitoring of heap and threads
Problems we fix
Problem
The application slows down and then restarts
What we do
We read GC logs and heap dumps to find a leak or a too-small heap, adjust settings and report the cause.
Problem
OutOfMemoryError in production
What we do
We check heap and metaspace, set sensible limits and heap dump options, and find what grows.
Problem
The Tomcat manager is exposed or default credentials exist
What we do
We remove or restrict it, rotate credentials and review the deployed applications.
Automatic tools, and our team for the rest
RootManage is automatic server management with every tool in one place. The tools run by themselves on a schedule and report to one dashboard. Everything they cannot do, and every emergency, is handled by our engineers by hand.
Automatic
RootManage tools, running by themselves
- Server Health agent reports load, disk use and failed login attempts to your dashboard.
- Metrics agent draws CPU, memory, disk and network charts, sampled every five minutes.
- Uptime checks check the server every minute and email you when it stops answering, and again when it recovers.
- LiteHouse runs a low-priority audit of your website at 04:00 IST and lists findings you can act on.
Manual, by our engineers
Everything else, and every emergency
- Hands-on work. Fixes, tuning, migrations, upgrades and the other jobs listed above on this page.
- Emergency work. A hacked site, an outage or a failed update is handled by a person who investigates and fixes it, not by a script.
- Things we do not automate. Anything the tools do not cover is done by hand, over SSH, WHM or RDP, on a login you can remove at any time.
The tools are optional, run on Linux servers and are installed by you with one command each. Every job our team does is recorded as a task in your dashboard with the details, and you get an email when it is updated.
How it works
- 1
Sign up
Create an account, choose a plan and add the server you want managed.
- 2
Install the tools
Run one command per tool. They then work by themselves and report to your dashboard. For hands-on work you give us a login you can remove at any time.
- 3
Automatic, with people behind it
The tools watch, scan and back up automatically and alert you. Our engineers do the rest by hand and handle every emergency, and you follow each task in your dashboard.
Questions about Java and Apache Tomcat
Do you manage Spring Boot apps run as a jar?
Yes. We run them as systemd services with limits, logs and health checks, and put Nginx in front.
Can you help us update from an old Java version?
We test the application on the newer Java in a copy and fix configuration issues; code changes are for your developers.
What does it cost to have Java and Apache Tomcat managed?
Managed plans start at ₹1,999 a month for one server, and Java and Apache Tomcat is managed as part of the server. The pricing page lists what each plan includes. If a server is already infected, the emergency cleanup is a one-time ₹9,000 job.