| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Req_active |
Current
number of threads servicing web requests
|
Number |
A
high value of this measure indicates a heavy load on the web module.
An increase in requests running may indicate an increase in user
workload. Alternatively, a slowdown of the application server may also
cause the requests that are simultaneously executing to increase. |
| Req_completed |
The
rate at which web requests are being processed by this application |
Reqs/Sec
|
A very high value for this measure indicates that the web module is
handling many requests.
|
| Avg_req_process_time
|
Average
time spent servicing web requests during the last measurement period |
Secs |
An
increase in this value may be indicative of a problem in the
application server. This increase could also be attributed to a
problem in database tier provided the application is using the
database for servicing the request. |
| Max_req_process_time
|
The
high water mark indicating the maximum time spend servicing a web request |
Secs |
|
| Avg_ctx_resolve_time
|
Average
time spent to create/find the servlet context during the last
measurement period. |
Secs |
A
very high value is an indication of heavy load on the web module. |
| Avg_req_parse_time
|
Average
time spent to read/parse requests during the last measurement |
Secs |
Comparing
the total request processing time with the context resolution time and
request parsing time, can provide an indication of where a request is
spending time in the Oracle application server instance. |