JBoss Sessions Test
For each web application deployed on the target WildFly JBoss server, this test reports the number of sessions that are active, rejected and expired. In addition, this test also reports the maximum number of active sessions the application can handle. This way, administrators are able to identify over load on the application and proactively rectify that before the application crashes. This test also reports the average alive time of sessions and percentage of session utilization. Thereby, this test helps to ensure that there are no bottlenecks in web request handling by each web applications due to low maximum sessions limit or high average alive time.
Target of the test : A WildFly JBoss server
Agent deploying the test : An internal agent
Outputs of the test : One set of results for each Web application deployed on the target WildFly JBoss that is to be monitored.
Parameters | 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 9990. |
SSL |
If the WildFly JBoss server being monitored is an SSL-enabled server, then set the SSL flag to Yes. If not, then set the SSL flag to No. |
Is JBoss Running In Domain Mode? |
Specify whether the server to be monitored is currently running in Domain Mode or not. By default, this flag is set to No which implies that the server is currently running in Standalone Mode. If you have started the target JBoss server using the default web profile configuration in domain mode i.e, if you have executed the ./domain.sh command from the <JBoss_INSTALL_DIR>/bin directory, then specify Yes against this flag. |
JBoss Host Name |
Specify whether the target server to be monitored is a master or a slave in a JBoss cluster. By default, none will be specified here which implies that the target JBoss server is a standalone server. Refer to Identifying the host name and server instance name of the WildFly JBoss server running in Domain mode to know how to identify whether the target server is a master or slave in your environment. |
JBoss Server Instance Name |
Specify the name of the server instance that is to be monitored. By default, none will be specified here. Refer to Identifying the host name and server instance name of the WildFly JBoss server running in Domain mode to identify the name of the server instance that is to be monitored. |
Management User and Management Password |
Specify the credentials of the user who is authorized to access the management console of the target JBoss server. To create a new user, refer to Creating a new management user in the WildFly JBoss server of this document. |
Confirm Password |
Confirm the Management Password by retyping it here. |
Measurement |
Description |
Measurement Unit |
Interpretation |
---|---|---|---|
Active sessions |
Indicates the number of active sessions on this web application. |
Number |
|
Expired sessions |
Indicates the number of sessions that have expired on this web application during the last measurement period. |
Number |
|
Max active sessions |
Indicates the maximum allowed number of concurrent sessions that this web application can handle. |
Number |
If the value of active sessions is more than maximum active sessions count, then that indicates a bottleneck condition. |
Rejected sessions |
Indicates the number of rejected sessions on this web application during the last measurement period. |
Number |
If the number of active sessions exceeds the configured maximum number of sessions allowed, then the attempts to create new sessions will be rejected. |
Average alive time |
Indicates the average time for which the expired sessions have been alive on this web application. |
Seconds |
|
Sessions created |
Indicates the total number of sessions created on this we application during the last measurement period. |
Number |
|
Sessions utilization |
Indicates the percentage of session utilization on this web application. |
Percent |
The value of this measure will be computed using the following formula: (Active session / Max active session ) *100 |