Agents Administration - Tests
 

Configuration of JvmMemPoolGCTest

This test enables administrators to guage the effectiveness of the garbage collection activity on the memory pools, and helps them accurately identify those memory pools where enough memory could not reclaimed or where the garbage collectors spent too much time.

Note:

This test will work only if the target Java application uses the JDK/JRE offered by one of the following vendors: Oracle, Sun, OpenJDK. IBM JDK/JRE is not supported.

The default parameters associated with this test are:

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

  • In the HOST text box, specify the host for which the test is to be configured.

  • Specify the port number at which the specified HOST listens in the PORT text box.

  • This test allows you the option to collect the desired metrics using one of the following methodologies:

    • By contacting the Java runtime (JRE) of the application via JMX
    • Using GC logs

    To use JMX for metrics collections, set the MEASURE MODE to JMX.

    On the other hand, if you intend to use the GC log files for collecting the required metrics, set the MEASURE MODE to Log File. In this case, you would be required to enable GC logging. The procedure for this has been detailed in Section 1.2.5.1 of the Monitoring Java Applications document.

  • The JMX REMOTE PORT parameter will be available only if the MEASURE MODE is set to JMX. Here, specify the port at which the JMX listens for requests from remote hosts. Ensure that you specify the same port that you configured in the management.properties file in the <JAVA_HOME>\jre\lib\management folder used by the target application.

  • The JNDINAME parameter will be available only if the MEASURE MODE is set to JMX. The JNDINAME is a lookup name for connecting to the JMX connector. By default, this is jmxrmi. If you have resgistered the JMX connector in the RMI registery using a different lookup name, then you can change this default value to reflect the same.

  • The USER, PASSWORD and CONFIRM PASSWORD parameters will be available only if the MEASURE MODE is set to JMX. If JMX requires authentication only (but no security), then ensure that the USER and PASSWORD parameters are configured with the credentials of a user with read-write access to JMX. To know how to create this user, refer to Section 1.1.1.2 of the Monitoring Java Applications document. Confirm the password by retyping it in the CONFIRM PASSWORD text box.

  • The JREHOME parameter will be available only if the MEASURE MODE is set to Log File. Specify the full path to the Java Runtime Environment (JRE) used by the target application.

  • The LOGFILENAME parameter will be available only if the MEASURE MODE is set to Log File. Specify the full path to the GC log file to be used for metrics collection.

  • If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

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

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.