Agents Administration - Tests
 

Configuration of MuleJmxMemTest

This test continuously monitors the JVM heap usage of each Mule application/domain and reports the percentage of memory utilized and amount of the available free memory. This way, the test forewarns administrators on possible memory contentions before it causes Out of Memory errors which in turn can increase the CPU usage due to full garbage collection events, and turn the application unresponsive.

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.

  • Specify Host name of the server for which the test is to be configured in the HOST text box.

  • Specify the port to which the specified host listens in the PORT text box.

  • To collect metrics from a Mule ESB, 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. Specify the port at which the jmx listens for requests from remote hosts in JMX REMOTE PORT text box. Ensure that you specify the same port that you configured in the ${MULE_HOME}/conf/wrapper.conf of the target application. For more details, refer to Click here.

  • By default, the JMX connector on the Mule ESB requires no authentication and security, in that case set the JMX USER and JMX PASSWORD parameters as none.

    If the JMX connector on the Mule ESB requires both authentication and security, then to enable the eG agent to use JMX, you need to configure the agent with the credentials of a user who is authorized to use JMX and has read only privileges. You can hence configure the JMX USER and JMX PASSWORD parameters with the credentials of a user with monitor role given in jmxremote.password and jmxremote.access files. To know the credentials of such a user, refer to Click here.

    Confirm the JMX PASSWORD you specify by retyping that password 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.

  • This test uses a JMX Provider to access the MBean attributes of the Mule ESB and collect metrics. Specify the package name of this JMX Provider in the JMX PROVIDER text box. By default, this is set to com.sun.jmx.remote.protocol.

  • Specify the duration (in seconds) for which this test should wait for a response from the Mule ESB in the TIMEOUT text box. If there is no response from the server beyond the configured duration, the test will timeout. By default, this is set to 1000 seconds.

  • If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS button will appear in this page. Clicking on this button 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.