Note: Although the script name mentions GlassFish Server, the script file can be used for troubleshooting any monitor connectivity issues, that comes under JMX mode of monitoring like JMXApplications, Apache Zookeeper, Apache Geronimo etc.,
This file is used to check if the connectivity and the Discovery of the Glassfish Server is possible from the Applications Manager installed server. This standalone program is a excerpt of the same process we use to add the Glassfish Server monitor. The usage to run this file is as below
Via command prompt, navigate to AppManager/bin/troubleshooting directory and execute the GlassFishDebug file with the usage mentioned below:
- GlassFishDebug.bat [HostName / Ip] [Port Number] [JndiPath] [Username] [Password]
Eg. GlassFishDebug.bat 193.xxx.xxx.xxx 8080 /jmxrmi admin admin
- GlassFishDebug.sh [HostName / Ip] [Port Number] [JndiPath] [Username] [Password]
Eg. GlassFishDebug.sh 193.xxx.xxx.xxx 8080 /jmxrmi admin admin
[HostName / Ip] HostName or Ipaddress of machine where GlassFish server is running
[Port Number] Port number of the GlassFish server
[Jndi Path] JndiPath for connecting to the GlassFish server
[Username] User name for connecting to GlassFish server
[Password] Password for connecting to GlassFish. If no password enabled, leave it as blank
This will initiate the process to discover the Glassfish Server and on success will also fetch the data for the default attributes monitored and shown as the output. From this you will be able to find If discovery is possible, If data is returned for all attributes or not. In case there is any issue for an attribute data it'll be shown as null. This infers that the data is not available in that server and has to be checked on the Glassfish installed server.
For more info or assistance do send us the output of the above command for analysis along with Support Information File.