To understand how much load is imposed by user sessions on each of the web applications deployed on the GlassFish server, and to determine the nature (e.g., persisted sessions, rejected sessions, etc.) and the current state of these sessions (whether activated, passivated, created, etc.), use the GfSessionTest test. This way, the most popular web applications on the server can be isolated, and those applications that reject sessions too often can be identified.

This page depicts the default parameters that need to be configured for the GfSessionTest.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed. 

• To collect metrics from a GlassFish Enterprise server, the eG agent monitoring that server should be configured to use JMX to connect to the JRE used by the server and pull out the metrics of interest. By default, JMX support is enabled for the JRE used by the GlassFish Enterprise Server. The JMX connector listens on port 8686 by default. Therefore, type 8686 as the JMX REMOTE PORT. If JMX listens on a different port in your environment, then specify the same here. To know the port at which JMX listens, open the domain.xml file in the <GLASSFISH_INSTALL_DIR>\Sun\AppServer\domains\domain1\config directory and look for the code block shown below:

  <jmx-connector accept-all=“false” address=“0.0.0.0” auth-realm-
  name=“admin-realm” enabled=“true” name=“system” port=“8686”
  protocol=“rmi_jrmp” security-enabled=“false”>

  The port number specified against the port parameter in the code block above refers to the JMX REMOTE PORT.

• By default, the JMX connector on the GlassFish Enterprise Server requires authentication. To enable the eG agent to use JMX therefore, you need to configure the agent with the credentials of a user who is authorized to use JMX. Typically, the GlassFish administrator has the right to use JMX. You can hence configure the JMX USER and JMX PASSWORD parameters with the credentials of the administrator. However, if you prefer not to expose the credentials of an administrator owing to security considerations, you can use the credentials of any other user with access rights to JMX. To know the name of such a user, open the domain.xml file in the <GLASSFISH_INSTALL_DIR>\Sun\AppServer\domains\domain1\config directory and look for the code block shown below:

  <jmx-connector accept-all=“false” address=“0.0.0.0” auth-realm-
  name=“admin-realm” enabled=“true” name=“system” port=“8686”
  protocol=“rmi_jrmp” security-enabled=“false”>

  The user name specified against the auth-realm-name parameter in the code block above can be configured as the JMX USER, and the password of that user can be specified against JMX PASSWORD.

• Confirm the JMX PASSWORD by retyping it in the CONFIRM PASSWORD text box.

• The JNDINAME is a lookup name for connecting to the JMX connector. By default, this is jmxrmi. If you have registered the JMX connector in the RMI registry using a different lookup name, then you can change this default value to reflect the same.

• Once the necessary values have been provided, clicking on the Update button will register the changes made.

When changing default configurations of tests, the values with "$" indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to "xyz" and $port will be changed to "80" when configuring a test.