I click the "Test" button, and after about 30 seconds, SAM reports that "Test failed with "unknown" status on " and "Cannot connect to JMX server". Next, from within the SAM Application Monitor edit page, I highlight one of the Component Monitors (i.e. 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. Since for testing purposes I'm not using credentials, I set "Credential for Monitoring" to. GlassFish is the Open Source Java EE Reference Implementation as such, we welcome external.
#FREE GLASSFISH HOSTING SERVER FOR MAC#
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. Download the latest version of GlassFish for Mac for free. Inside SAM, I added the Glassfish Application Monitor to the appropriate host. It works flawlessly and I am able to see all the usual metrics for things like heap size, thread count, etc. authenticate=falseĪfter restarting the Glassfish domain, I tested that configuration by using jconsole to connect directly to the Glassfish server via JMX.
I configured the following options within Glassfish as recommended in the Glassfish SAM guide ( ): Here are the steps I used to set the monitoring up: Can anyone suggest next steps for troubleshooting, or spot anything I might have overlooked?
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".
0 kommentar(er)
