Default Parameters for GFireMStatTest

By closely monitoring the reboot status, CPU usage, throughput and the I/O activity of each member, and comparing these metrics across members, you can quickly isolate resource-intensive members.

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

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

• In the JMXPORT, 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 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 registery using a different lookup name, then you can change this default value to reflect the same. 

• If JMX requires authentication only (but no security), then ensure that the JMX USER NAME and JMX 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 the Monitoring Java Application document.

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

• Specify the name of the server if the monitored GemFire server belongs to a cluster in the GEMFIRE SERVERS text box. By default, this is none.

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