Configuration of TomcatExecutorTest

This test auto-discovers Executor thread pools, and monitors the load, usage, and configuration of each pool. In the process, the test pinpoints pools that consistently process a large number of tasks, but do not have the processing power to service these tasks effectively causing many tasks to be enqueued in the Executor queue. The test also reports the current configuration of every pool, thus pointing administrators to those pools that are not configured according to their task load. This way, the test prompts administrators to fine-tune the pool configuration, so as to improve load processing.

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

• 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 IP address of the host for which this test is to be configured.

• In the PORT text box, specify the port at which the specified HOST listens to.

• This test can extract metrics from Tomcat using either of the following mechanisms:

  • By deploying the egtomcat.war file in the <EG_INSTALL_DIR>\lib directory of the eG agent host on the Tomcat server;

  • By contacting the Java runtime (JRE) of Tomcat via JMX

  To configure the test to use egtomcat.war file, first select the War file option from the MEASUREMENT MODE list. Then, refer to the How Does eG Enterprise Monitor Tomcat Servers?section in the Monitoring Tomcat Server document to know how to deploy the WAR file on the target Tomcat server.

  On the other hand, if you want the test to use JMX instead, then first, select the JMX option from the MEASUREMENT MODE list. Then, follow the procedure detailed in the How Does eG Enterprise Monitor Tomcat Servers?section in the Monitoring Tomcat Server document to configure the test to use jmx. By default, the JMX option is chosen here.

• The JMX USER, JMX PASSWORD, and CONFIRM PASSWORD parameters appear only if the Measurement Mode is set to JMX. If JMX equires authentication only (but no security), then ensure that the JMX User 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 How Does eG Enterprise Monitor Tomcat Servers? section in the Monitoring Tomcat Server document. Confirm the password by retyping it in the CONFIRM PASSWORD text box.

• The JNDI NAME parameter appears only if the Measurement 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 registered the JMX connector in the RMI registery using a different lookup name, then you can change this default value to reflect the same.

• The PROVIDER parameter appears only if the Measurement Mode is set to JMX. This test uses a JMX Provider to access the MBean attributes of the target Java application and collect metrics. Specify the package name of this JMX Provider here. By default, this is set to com.sun.jmx.remote.protocol.

• The SSL parameter appears only if the Measurement Mode is set to War File. Indicate Yes if the Tomcat server is SSL-enabled.

• The URL parameter appears only if the Measurement Mode is set to War File. Specify the URL of the managed Tomcat server to enable the test to connect to it and extract measures from it. The URL specification should be of the format: http://{TomcatIP}:{TomcatPort}.

• The USERNAME, PASSWORD, and CONFIRM PASSWORD parameters appear only if the Measurement Mode is set to War File. In the USERNAME text box, specify a name of a user who has been assigned the Manager role on the Tomcat server to be monitored; these users are typically allowed to control web applications deployed on the Tomcat server. Specify the PASSWORD of this user, and confirm the password by retyping it in the CONFIRM PASSWORD text box.

• The ENCRYPTPASS parameter appears only if the measurement modeis set to War File. Select Yes if you want to encrypt the password.

• In the TIMEOUT text box, specify the duration (in seconds) for which this test should wait for a response from Tomcat. If there is no response from Tomcat beyond the configured duration, the test will timeout. By default, this is set to 240 seconds.

• 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 above values are provided, click on the UPDATE button to 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.