Agents Administration - Tests
 

Default parameters for JvmMemoryLeakTest

This test continuously monitors the JVM heap usage and promptly alerts administrators when memory usage crosses a configured limit.

Note:

This test will work only if the following pre-requisites are fulfilled:

  • The test should be executed in an agent-based manner only.

  • The target Java application should use the JDK/JRE offered by one of the following vendors only: Oracle, Sun, OpenJDK. IBM JDK/JRE is not supported.

  • The monitored Java application should use JDK/JRE 1.6 or higher.

  • For this test to run and report metrics, the eG agent install user should be the same as the Java application (or) Java web/application server install user.

  • By default , this test programmatically dumps a heap dump (.hprof files) in the folder  <EG_AGENT_INSTALL_DIR>\agent\logs folder. To enable the eG agent to read/analyse such files, you need to add the eG agent install user to the Java application (or) Java web/application server install user group. If this is not done, then the dump files will be created, but will not be processed by the eG agent, thus ending up unnecessarily occupying disk space (note that .hprof files are normally 1-5 GB in size).

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

  • The TEST PERIOD list box helps the user to decide how often this test needs to be executed. By default, this is set to 1 hour.

  • This test counts all those classes that are consuming memory beyond the limit (in percentage) specified against PCT HEAP LIMIT as ‘memory leak suspects’. This count is reported as the value of the Leak suspect classes measure. By default, 30 (%) is the PCT HEAP LIMIT. This implies that the test, by default, reports each class that consumes over 30% of the Allocated heap memory as a Leak suspect class. Such classes are listed as part of detailed diagnostics.

  • For the eG agent to collect metrics from the target IBM WebSphere Liberty server, the local connector should be enabled on the target server. Once the connector is enabled, a com.ibm.ws.jmx.local.address file will be created in the ${server.output.dir}/logs/state folder. The eG agent uses this file to connect to the target server and collect the required metrics from it. Therefore, specify the exact path to this file in the SERVICE URL PATH text box. For example, in case of Windows environments, the Service URL Path can be C:\wlp\usr\servers\server1\logs\state and in case of Linux environments, the SERVICE URL PATH can be /opt/wlp/ur/servers/server1/logs/state.

  • Specify the duration (in seconds) for which this test should wait for a response from the target Java application. If there is no response from the target beyond the configured duration, the test will timeout. By default, the TIMEOUT parameter is set to 240 seconds.

  • The DD FREQUENCY refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against this parameter.

  • 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.