Tomcat Manager status and JMX monitoring alert overlap

Answer

Use the Manager status endpoint for application‑level conditions that change relatively infrequently – active session anomalies and reload counts – and use the JMX ThreadPool MBean for real‑time thread saturation.

Confirmed facts

• Manager status (XML/JSON) provides activeSessions, reloadCount, processingTime.
• JMX exposes Catalina:type=ThreadPool,name="http‑nio‑8080" with currentThreadsBusy and maxThreads.
• The Session manager MBean (Catalina:type=Manager,...) duplicates activeSessions but with higher frequency.

Likely explanation

Thread‑busy metrics fluctuate every second; polling them via JMX yields timely alerts for exhaustion. Session counts and reloadCount change only on deployments or user‑flow shifts, so less frequent polling via Manager status avoids duplicate alerts from the same underlying condition.

Steps to avoid duplicate alerts

1. Disable thread‑saturation alerts on Manager status; enable them only on the JMX ThreadPool MBean (alert when currentThreadsBusy > 0.9 × maxThreads for two consecutive polls).
2. Enable session‑anomaly and reload alerts on Manager status (or the Manager MBean if you already poll JMX for sessions) – e.g., alert when activeSessions > threshold or reloadCount increments unexpectedly.
3. If you already collect JMX for other reasons, you can replace Manager status session checks with the Manager MBean activeSessions attribute to keep a single data source.
4. Correlate session growth with thread usage by joining Manager status activeSessions (or Manager MBean) with JMX currentThreadsBusy in your alerting engine using a time‑windowed (e.g., 5‑minute) join; raise a combined alert when session rise precedes thread exhaustion.

Verification (safe, scoped)

# Check JMX ThreadPool attributes
jconsole -J-Djava.util.logging.config.file=logging.properties service:jmx:rmi:///jndi/rmi://localhost:9010/jmxrmi
# or with jcmd
jcmd  ManagementAgent.start localonly=false
# View Manager status
curl -s http://localhost:8080/manager/status?XML | xmllint --format -

Replace localhost:8080 and 9010 with your host and JMX port. Ensure authentication is enabled before exposing these endpoints.

Missing diagnostic detail

Please confirm the polling interval used by your monitoring system; if it exceeds 30 seconds, favor Manager status for session alerts, otherwise JMX can be used for near‑real‑time thread metrics.