GlassFish monitor

Supported versions

NeoLoad supports all GlassFish server versions, but some counters may not be available for versions 2.0.x and earlier.

Connection settings

Defining a monitor on a GlassFish server requires the name or IP address of the machine to be monitored, as well as the connection port (the default port is 8686). The port is the GlassFish server JMX connection port.

In addition to these settings, a valid user account must be provided if authentication is enabled (same account than the one used to connect to GlassFish Administration Console). The default account is "admin" and the password "adminadmin".

To retrieve all the selected performance counters, NeoLoad requires the GlassFish server monitoring level to be set to "high". To display the server monitoring levels, enter the following command from the server bin directory:

asadmin get server.monitoring-service.module-monitoring-levels.*

server.monitoring-service.module-monitoring-levels.connector-connection-pool = OFF 
server.monitoring-service.module-monitoring-levels.connector-service = OFF
server.monitoring-service.module-monitoring-levels.ejb-Container = OFF
server.monitoring-service.module-monitoring-levels.http-service = OFF 
server.monitoring-service.module-monitoring-levels.jdbc-connection-pool = OFF
server.monitoring-service.module-monitoring-levels.jms-service = OFF 
server.monitoring-service.module-monitoring-levels.jvm = OFF 
server.monitoring-service.module-monitoring-levels.orb = OFF 
server.monitoring-service.module-monitoring-levels.thread-pool = OFF 
server.monitoring-service.module-monitoring-levels.transaction-service = OFF 
server.monitoring-service.module-monitoring-levels.web-Container = OFF

To change monitoring level, enter the following commands from the server bin directory:

asadmin set server.monitoring-service.module-monitoring-levels.connector-connection-pool=HIGH 
asadmin set server.monitoring-service.module-monitoring-levels.connector-connection-pool=HIGH 
asadmin set server.monitoring-service.module-monitoring-levels.connector-service=HIGH 
asadmin set server.monitoring-service.module-monitoring-levels.ejb-Container=HIGH 
asadmin set server.monitoring-service.module-monitoring-levels.http-service=HIGH 
asadmin set server.monitoring-service.module-monitoring-levels.jdbc-connection-pool=HIGH 
asadmin set server.monitoring-service.module-monitoring-levels.jms-service=HIGH 
asadmin set server.monitoring-service.module-monitoring-levels.jvm=HIGH 
asadmin set server.monitoring-service.module-monitoring-levels.orb=HIGH 
asadmin set server.monitoring-service.module-monitoring-levels.thread-pool=HIGH 
asadmin set server.monitoring-service.module-monitoring-levels.transaction-service=HIGH 
asadmin set server.monitoring-service.module-monitoring-levels.web-Container=HIGH
Create a GlassFish monitor

NeoLoad makes it possible to create a new monitor either using the monitored machine creation wizard, as described in Create and configure a monitored machine, or from an existing monitored machine, as described in Create and configure a monitor.

NeoLoad displays a list of the WARs (Web application ARchive) deployed on the configured server. It then automatically selects the most appropriate counters for each of the selected applications.

Available counters

All GlassFish counters are documented here. Depending on the GlassFish monitoring level set, some counters may be automatically hidden because they are not offered by the GlassFish server.

Warning: For NeoLoad to monitor message services, the following monitoring module must be activated: server.monitoring-service.module-monitoring-levels.jms-service