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

Broken JMX monitors

Hi, after upgrading to Orion 2019.2 HF3 and SAM 6.9.1 our JMX monitors broke. When I test the monitors on the node it just stays at "Testing against..." indefinitely.

I used jconsole.exe on the main and additional pollers and I can connect to the JMX server just fine.

Any recommendations? Any logs you could point me to?

Thank you,

Find more posts tagged with

Accepted answers

ronmanp

Had to reinstall the additional pollers to fix it.

All comments

sturdyerde

I don't have an answer, but maybe my follow-up question will help bump your thread... What information from JMX do you monitor? Performance? Memory? We have a number of 3rd party Java apps in our environment, and I'm wondering if some JMX monitors would be helpful at all for us.

ronmanp

Memory heap used, Memory Heap Max size, Max processor time, active sessions, active connections, total available DB connections, total active DB connections.

Then we use Perfstack to analyse trends and troubleshoot issues within the Java app.

jrouviere

We've been having an issue with JMX monitoring for a while, but not this symptom.

To start, you should turn on debugging and review the application template logs to see if there is an error or something else.

Success Center

If you can open a case from there and/or provide us with a snippet from the logs we might be able to help from there.

sturdyerde

Hmm, I'm going to have to set this up for 2 applications in particular.

hpstech

Works good for us for DEVs that want Memory threshold alerts.

ronmanp

Had to reinstall the additional pollers to fix it.