eG MultiThread Pools Test
This test monitors the usage and performance of thread pools, tracking metrics such as pool size, active threads, queue size, and utilization. This helps administrators identify bottlenecks, prevent resource overloading, and ensure smooth system performance.
Target of the test : The eG Manager
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of results for the eG manager being monitored
| Parameter | Description |
|---|---|
|
Test period |
How often should the test be executed . |
|
Host |
The host for which the test is to be configured. |
|
Port |
The port number at which the specified host listens. |
|
JMX Remote Port |
Here, specify the port at which the JMX listens for requests from remote hosts. In the <EG_MANAGER_INSTALL_DIR>\manager directory (on Windows; on Unix, this will be the /opt/egurkha/manager directory) of the eG manager, you will find a management.properties file. Set the port defined against the com.sun.management.jmxremote.port parameter of the file as the JMX Remote Port. |
|
User, Password, and Confirm Password |
By default, JMX requires no authentication or security. Therefore, the User, Password , and Confirm Password parameters are set to none by default. |
|
JNDIName |
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. |
|
JMX Provider |
This test uses a JMX Provider to access the MBean attributes of the eG manager and collect metrics. Specify the package name of this JMX Provider here. By default, this is set to com.sun.jmx.remote.protocol. |
|
Timeout |
Specify the duration (in seconds) for which this test should wait for a response from the eG manager. If there is no response from the eG manager beyond the configured duration, the test will timeout. By default, this is set to 240 seconds. |
|
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
| Measurement | Description | Measurement Unit | Interpretation |
|---|---|---|---|
|
Queue max capacity |
Indicates the maximum number of threads that the queue can hold at any given time. |
Number |
The value of this measure denotes the upper limit of the queue's storage capacity, beyond which new items may be rejected or delayed. Monitoring this helps ensure that the system is properly sized to handle workload peaks without performance degradation. |
|
Queue current size |
Indicates the number of threads that are currently present in the queue. |
Number |
|
|
Queue utilization |
Indicates the percentage of the queue’s capacity that is currently in use. |
Percent |
A high value for this measure indicates that the queue is nearing its limit, which could lead to delays or processing bottlenecks if not addressed immediately. |
|
Core pool size |
Indicates the number of core threads in the thread pool that are maintained and kept alive, even if they are idle. |
Number |
|
|
Pool max capacity |
Indicates the maximum number of threads that the thread pool can create to handle tasks. |
Number |
|
|
Active threads count |
Indicates the number of threads in the pool that are currently active and executing tasks. |
Number |
|
|
Pool utilization |
Indicates the percentage of the pool’s capacity that is currently in use. |
Percent |
|