Jboss Thread Pools Test
This test monitors the thread pools in the JBoss server.
Target of the test : A JBoss application server
Agent deploying the test : An internal agent
Outputs of the test : One set of results for each thread pool configured in the JBoss 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 number at which the specified host listens to. |
Measurement Mode |
This test can extract metrics from JBoss using either of the following mechanisms:
To configure the test to usethe EgJBossAgent.sar and egjboss.war files, first, select the War File option. Then, refer to the How to Monitor JBoss Application Server Using eG Enterprise? chapter to know how to deploy these files on the target JBoss server. On the other hand, if you want the test to use JMX instead, then first, select the jmx option. Then, follow the procedure detailed in the How to Monitor JBoss Application Server Using eG Enterprise? chapter to configure the test to use jmx. By default, the jmx option is chosen here. |
JNDIName |
This 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 registry using a different lookup name, then you can change this default value to reflect the same. |
JMX Remote Port |
This parameter appears only if the Measurement Mode is set to jmx. Here, 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 of the target JBoss server (refer to the How to Monitor JBoss Application Server Using eG Enterprise? chapter for more details). |
JMX User, JMX Password, and Confirm Password |
These parameters appear only if the Measurement Mode is set to jmx. If JMX requires 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 to Monitor JBoss Application Server Using eG Enterprise? chapter. Confirm the password by retyping it in the Confirm Password text box. |
SSL |
This parameter appears only if the Measurement Mode is set to War File. Indicate Yes if the JBoss server is SSL-enabled. |
URL |
This parameter appears only if the Measurement Mode is set to War File. Specify the URL to be accessed to collect metrics pertaining to the JBoss server. By default, this test connects to a managed JBoss server and attempts to obtain the metrics of interest by accessing the local Mbeans of the server. Accordingly, by default, this parameter is set to http://<JBossServerIP>:<JbossServerPort>. |
JMX Provider |
This parameter appears only if the Measurement Mode is set to jmx. This test uses a JMX Provider to access the MBean attributes of the JBoss server 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 JBoss server. If there is no response from the server beyond the configured duration, the test will timeout. By default, this is set to 240 seconds. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Current busy threads |
Indicates the number of threads that are currently busy. |
Number |
The value of this measure serves as a good indicator of server workload. |
Current thread count |
Indicates the number of threads currently spawned in the JVM. |
Number |
|
Min spare threads |
Indicates the minimum number of spare threads. |
Number |
|
Max spare threads |
Indicates the maximum number of spare threads. |
Number |
|
Max threads |
Indicates the maximum number of threads that this pool can contain. |
Number |
If the number of threads in a pool grows close to the value of this measure, it indicates that the number of threads in the pool needs to be increased for effective operation of this application. Alternatively, you may also consider changing the maximum number of threads that a pool can contain. However, exercise caution when altering the maximum thread count, as a very high thread count can cause the app to slowdown from excessive memory usage. Likewise, if the maximum thread count is set too low, it will cause requests to block or timeout. |