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

JMX monitored failed

yangy

Hello,

My environment is as below:

-Target tomcat 7.0.82.0 installed on linux box

-My solarwinds:SAM 6.8.0, Orion platfrom 2018.4 HF3

I was trying to monitor target tomcat via JMX monitor. Already enabled jmxremote monitoring on my tomcat. Currently,

1. Using jconsole, I can connect and get the data from my tomcat successfully;

2. While when I configured and tested in my solarwinds, always got the error:

"Test failed with "Down" status on xxxx

Couldn't connect to JmxTermSvc"

1. What does "JmxTermSvc" mean here?

2. How to correct the issue? It seesm the issue is at solarwindws side as I can get the data via jconsole.

I am looking forward to your advice. Thanks in advance.

Yang

Find more posts tagged with

Accepted answers

All comments

mburgeso

Yang,

We had the same issue after any upgrade to from SAM 6.7 to SAM 6.9.1 where the JMX Connection was failing in Solarwinds.

As you can probably guess, having JMX functionality down is a MAJOR impact to APM monitoring since it is the eyes into the Java processes and when the MBean attributes are not obtained then the monitors/alert triggers are not working.

I resolved this as follows and it was quite simple:

1) I first proved that the JConsole was able to connect.

This proved that the JMX connection string is fine and the ports are open.

2) Ensured the Linux Agent was up-to-date with the SAM module.

Corrected this where it wasn't.

Still no luck with the JMX connections.

3) Placed an incident with Solarwinds Support.

They responsed rather quickly but their knowledge ended was just a rehash of what I already had tried and the person was friendly but lacked linux knowledge.

4) Created a copy of the JMX Template with a limited number of MBean attributes being read.

5) Played around with the settings a bit and finally determined that it was the under the Advanced Settings.

In particular, the "Preferred Polling Method".

Change this from "Agent" to "Agentless" and retested the JMX for a single linux server.

This worked for me.

Regards,

Mark

omavel

Change this from "Agent" to "Agentless" and retested the JMX for a single linux server.

Thank you, this worked for me too