Hi all,
I'm trying to set up SAM to monitor a Glassfish (version 3.1.2.2 build 5) domain, but when I configure the Application Monitor with the details of the server I want to monitor and test the Component Monitor within SAM, it fails with the error "Cannot connect to JMX server". Can anyone suggest next steps for troubleshooting, or spot anything I might have overlooked?
Here are the steps I used to set the monitoring up:
I configured the following options within Glassfish as recommended in the Glassfish SAM guide (http://thwack.solarwinds.com/docs/DOC-167307):
-Djava.rmi.server.hostname=192.168.100.100
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=6800
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
After restarting the Glassfish domain, I tested that configuration by using jconsole to connect directly to the Glassfish server via JMX. It works flawlessly and I am able to see all the usual metrics for things like heap size, thread count, etc.
Inside SAM, I added the Glassfish Application Monitor to the appropriate host. Then, because I am using a non-default port for JMX, I edited the Component Monitors to change the port from the template's default to my domain's corresponding port, 6800. Since for testing purposes I'm not using credentials, I set "Credential for Monitoring" to <none>. All other Component Monitor configuration values have been left at the template's defaults, except that I have also tried changing the Component Monitor's protocol from RMI to IIOP without success.
Next, from within the SAM Application Monitor edit page, I highlight one of the Component Monitors (i.e. Memory Heap Used (B)). I click the "Test" button, and after about 30 seconds, SAM reports that "Test failed with "unknown" status on <server-name>" and "Cannot connect to JMX server".