Request monitoring
You can use the RequestTimingStats MXBean to collect request data to see how the Liberty server is performing in comparison with set goals.
Servlet requests that are identified by the name of Servlet are tracked.
The object name that identifies the MXBean is WebSphere:type=RequestTimingStats,name=*. An
example is WebSphere:type=RequestTimingStats,name=Servlet.
The following table lists attributes in the RequestTimingStats MXBean and the data available for
each of these attributes.
| Attribute | Data available |
|---|---|
| RequestCount | A long value that represents the total requests since the server started |
| ActiveRequestCount | A long value that represents the total number of requests currently running. |
| SlowRequestCount | A long value that represents the total requests that are running and that are deemed slow. |
| HungRequestCount | A long value that represents the total requests in flight that are deemed hung. |
The slow and hung request counts are refreshed less frequently than the active request count. At times the slow or hung request count that is returned by the MXBean might be greater than the active request count returned by the MXBean. This discrepancy resolves itself after a short time.