SunOne JDBC Test
This test reports the performance metrics related to the JDBC connection pools of a Sun Java System application server.
Target of the test : Any Sun Java System application server
Agent deploying the test : An internal agent
Outputs of the test : One set of results for every JDBC connection pool.
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 on which the Sun Java System application server is running. |
User |
A valid user name for the Sun Java System server to be monitored. |
Password |
Password for the Sun Java System server to be monitored. |
Admin Port |
The port number on which the “asadmin” tool runs. |
Server |
Name of the Sun Java System server to be monitored. |
AppServerDir |
The directory in which Sun Java System application server is installed. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Waiting threads |
The number of threads that are waiting for a database connection.
|
Number |
Ideally, this measure should have a low value. A high value of this measure indicates that the database is slow or does not have additional connections to allocate to service requests from the web application server. |
Connections failed |
The total number of times a thread has failed to acquire a JDBC connection. |
Number |
This value can increase for various reasons – connection failures can happen if the database server is down or if the maximum limit of simultaneous connections possible has been reached. Alternatively, if the database pool is not adequately sized (i.e., too few maximum connections), connection failures can occur. |
Connection timeouts |
The total number of connection requests that have been timed out. |
Number |
Ideally, this measure should have a low value. A high value of this measure indicates that the database is slow or does not have additional connections to allocate to service requests from the web application server. |