JEUS Thread Pools Test
To optimize performance and at the same time to support concurrent accesses from users, the application server uses thread pools. It is critical to monitor a JEUS’s thread pools on an ongoing basis. This is what exactly the JEUS Thread Pools test does. By continuously monitoring the thread pools of the JEUS server, administrators can figure out the number of active threads in each thread pool and the size of the thread pool. Additionally, this test also reveals the Using this test, administrators can determine the thread pool containing the maximum number of active threads.
Target of the test : A JEUS Web Application server
Agent deploying the test : An internal agent
Outputs of the test : One set of results for each thread pool on the target server.
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 at which the specified host listens. By default, this is 9736. |
Username and Password |
To enable the eG agent to communicate and continuously monitor the target JEUS server, the eG agent should be configured with the credentials of the admin user on the server. In highly-secure environments, administrators may not want to expose the credentials of the user possessing administrator privileges. In such environments, for monitoring the JEUS application server, administrators have an option to create a new user on the JEUS server and assign administrator privilege to that user. The steps to create a new user with administrator privilege are explained in Creating a User with Administrator Privileges |
Confirm Password |
Confirm the Password by retyping it here. |
Listener Port |
To collect metrics from the target server, the eG agent should be configured to use JMX to connect to the JRE used by the target server and pull out the performance metrics. By default, JMX support is enabled for the JRE used by the target server. The JMX connector listens on port 9736, by default. Therefore, type 9736 as the Listener Port. However, if the host is configured with multiple sever instances, then you should specify the port number at which the JMX listens in your environment. Ensure that you specify the same port that you configured while creating the listener (if required) using the JEUS WebAdmin Console. To know the details on the listener port, refer to Enabling JMX Support for the JEUS Web Application Server |
Export name |
The export name is the reference name of the RMI connector that is to be used as a JMX connector. The procedure to obtain the export name is detailed in Enabling JMX Support for the JEUS Web Application Server |
Server name |
Provide the name of the sever instance that is being monitored in the Server Name text box. Also, ensure that the JVM monitoring is enabled for the target server. To obtain the name of the server instance, refer to Enabling JMX Support for the JEUS Web Application Server |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Pool size |
Indicates the number of threads in this pool. |
Number |
This measure is a good indicator of load on the thread pool. If the pool size is high and the number of active threads is low, it signifies that the threads are not being destroyed immediately after use. |
Core pool size |
Indicates the current number of core threads in this pool. |
Number |
|
Active pools |
Indicates the number of threads that are currently active in this pool. |
Number |
Comparing the value of this measure across the thread pools helps administrators identify the thread pool containing the maximum number of active threads. |
Current tasks |
Indicates the number of tasks processed by the threads in this pool during the last measurement period. |
Number |
This measure is a good indicator of how busy the pool was during the last measurement period. |
Maximum pool size |
Indicates the maximum number of threads allowed in this pool. |
Number |
|
Thread execution time |
Indicates the time taken to execute the threads in this pool during the last measurement period. |
Sec |
|
Queue waiting size |
Indicates the number of threads in this pool that are currently waiting for tasks in the queue. |
Number |
|
Queue waiting time |
Indicates the time duration for which the threads were waiting in this pool for task execution. |
Sec |
|