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 monitored Java application uses JRE 1.6 or higher.
This page depicts the default parameters that need to be configured for the JvmMemoryLeakTest.
This test can extract metrics from the Java application using either of the following mechanisms:
- Using SNMP-based access to the Java runtime MIB statistics;
- By contacting the Java runtime (JRE) of the application via JMX
To configure the test to use SNMP, select the SNMP option. On the other hand, choose the JMX option to configure the test to use JMX instead. By default, the JMX option is chosen in the MODE text box.
The JMX REMOTE PORT parameter appears only if the 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.
By default, JMX requires no authentication or security. Therefore, the USER, PASSWORD, and CONFIRM PASSWORD parameters are set to none by default.
The JNDINAME parameter appears only if the 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.
By default, the eG agent supports SNMP version 1. Accordingly, the default selection in the SNMPVERSION list is v1. However, if a different SNMP framework is in use in your environment, say SNMP v2 or v3, then select the corresponding option from this list. The community string of the Cisco device has to be provided in the SNMPCOMMUNITY text box. This parameter is specific to SNMP v1 and v2 only. Therefore, if the SNMPVERSION chosen is v3, then this parameter will not appear. The USERNAME parameter appears only when v3 is selected as the SNMPVERSION. SNMP version 3 (SNMPv3) is an extensible SNMP Framework which supplements the SNMPv2 Framework, by additionally supporting message security, access control, and remote SNMP configuration capabilities. To extract performance statistics from the MIB using the highly secure SNMP v3 protocol, the eG agent has to be configured with the required access privileges - in other words, the eG agent should connect to the MIB using the credentials of a user with access permissions to the MIB. Therefore, specify the name of such a user against the USERNAME parameter. Specify the password that corresponds to the above-mentioned USERNAME in the AUTHPASS text box. This parameter once again appears only if the SNMPVERSION selected is v3. Confirm the AUTHPASS by retyping it in the CONFIRM PASSWORD text box. The AUTHTYPE parameter too appears only if v3 is selected as the SNMPVERSION. From the AUTHTYPE list box, choose the authentication algorithm using which SNMP v3 converts the specified USERNAME and PASSWORD into a 32-bit format to ensure security of SNMP transactions. You can choose between the following options
- MD5 - Message Digest Algorithm
- SHA - Secure Hash Algorithm
The ENCRYPTFLAG appears only when v3 is selected as the SNMPVERSION. By default, the eG agent does not encrypt SNMP requests. Accordingly, the ENCRYPTFLAG is set to NO by default. To ensure that SNMP requests sent by the eG agent are encrypted, select the YES option. If the ENCRYPTFLAG is set to YES, then you will have to mention the encryption type by selecting an option from the ENCRYPTTYPE list. SNMP v3 supports the following encryption types:
- DES - Data Encryption Standard
- AES - Advanced Encryption Standard
Specify the encryption password in the ENCRYPTPASSWORD text box. Confirm the encryption password by retyping it in the CONFIRM PASSWORD text box. Specify the duration (in seconds) within which the SNMP query executed by this test should time out in the TIMEOUT text box. The default is 10 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 DD FREQUENCY.
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.
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.
|