Issues using JMX monitoring on Linux

Been attempting to monitor Java JMX on a linux server and so far we cannot get the browser to accept the protocol, port, or username/password combination. We've tried various ideas from thwack, tried switching to an agent based communication, and tried snmp, but so far nothing. Has anyone been successul configured jmx on linux to be able to monitor mbeans? What's the secret?

Find more posts tagged with

java jmx

linux server

Accepted answers

All comments

mesverrum

I've done it before, I don't have access to that client environment right now but I'll be there again in 2 weeks and if nobody has weighed in I'll pull up the sample configs.

One thing to make sure of is that there is a built in mbeans browser from java called Jconsole, if you can't get this working then Orion is not going to do you any good. Once you get this in place then basically you can just duplicate all the settings you used there within Orion and you are golden.

Using JConsole - Java SE Monitoring and ManagementGuide

aLTeReGo

The following post should walk you through the process

Understanding Java Remote JMX - Initial Setup/Config Overview

There is also an excellent guide available here > Configuring and Integrating JMX.pdf

mburgeso

I spilt this setup into two pieces, mainly because each piece has a different owner: Server-Side setup and Solarwinds setup.

Server-Side JMX setup

1) Enable the JVM attributes for JMX and also setup a Username/Password for remote authentication.

Configure the JMX attributes in the JVM settings:

-Dcom.sun.management.jmxremote.port=9999 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.password.file=jmxremote.password

Set the JMX UserName & Password in the jmx

There are two files that will need to be changed to enable basic authentication: jmxremote.access and jmxremote.password

jmxremote.access - defines the users and access levels for the JMX authentication.

- You should ONLY use the readonly access for JMX monitoring.

- e.g. monitorRole readonly

jmxremote.password - defines the passwords for the usernames in the jmxremote.access file.

- e.g. monitorRole 123monitorPswd#

2) Test the connectivity of the JMX protocol by testing the JMX username/password with the JConsole utility.

3) Once the above steps test out okay then the JVM owner will need to supply the Monitoring Team with the Host:Post, Connectivity String, and Username/Password.

NOTE: Start with basic authentication then once that is working you may harden the security if you wish.

Solarwinds Setup

1) Setup the JMX Credentials in the SAM Credentials Library.

2) Add servers to the existing Application JMX template OR make a copy of that template.

3) Verify that the connectivity is working from the JVM to Solarwinds and verify that the JMX attributes are being populated in the Solarwinds database.

4) Now that the above steps are complete, you can use the new JMX attributes from the Solarwinds database to create dashboard panels just like any other dashboard.