Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

How do I monitor for Tomcat being down with JMX?

Sounds like a silly thing, but when the Tomcat app on the Linux server is down, SAM's JMX template just goes to Unknown and SolarWinds never sets the application to Down. All components getting "Network connection failed. Cannot connect to JMX server" does not make Solarwinds think Down, just Unknown.

Find more posts tagged with

Accepted answers

All comments

The JMX Monitor goes into an "Unknown" because it could be a connectivity issue, and not that the Tomcat application is really down. It's preferable to rely on something else that provides an affirmative response that the server is in fact reachable, but a critical process is not running. I this case I would recommend using one of SAM's process/service monitors to monitor the Tomcat daemon for status (up/down). JMX should be used primarily for performance and statistic collection purposes only.

Quick Links