You can monitor limiter statistics using the rhino-stats tool or the StatsManagement MBean.
The root parameter set is called Limiters, and it has one child parameter set for each limiter; for example, Limiters.SystemInput or Limiters.QueueSaturation.
Limiter parameters recorded
Rhino records the following limiter parameters:
| Records the total number of.. | Increments.. | Decrements.. |
|---|---|---|
Total units successfully used or forced — |
||
…units allowed to be used and units forced to be used. |
…whenever units are allowed to or forced to be used. |
…never. |
Total units denied by a limiter’s parent — |
||
…units not allowed to be used, because the parent of the limiter denied their use. This includes units denied because of any ancestor (such as the parent of the parent). The |
…whenever the parent of a limiter denies unit use. |
…never. |
Total units denied by a limiter — |
||
…units not allowed to be used, because a limiter or its parent denied their use. This includes units denied because of any ancestor (such as the parent of the parent). |
…whenever a limiter denies unit use. |
…never. |
Example
The following excerpt shows the number of units a limiter allows and rejects, second by second.
$ ./rhino-stats -m Limiters.SystemInput
2009-03-11 06:57:43.903 INFO [rhinostat] Connecting to localhost:1199
2009-03-11 06:57:44.539 INFO [dispatcher] Establish direct session DirectSession[host=server1 port=17400 id=56928181032135173]
2009-03-11 06:57:44.542 INFO [dispatcher] Connecting to localhost/127.0.0.1:17400
Limiters.SystemInput
time rejected rejectedByParent used
----------------------- ---------------------------------
2009-03-11 06:57:46.604 - - -
2009-03-11 06:57:47.604 14 0 103
2009-03-11 06:57:48.604 14 0 102
2009-03-11 06:57:49.604 11 0 101
2009-03-11 06:57:50.604 12 0 99
2009-03-11 06:57:51.604 13 0 102
2009-03-11 06:57:52.604 14 0 101
2009-03-11 06:57:53.604 8 0 96
(In this example, rejectedByParent is 0, as SystemInput has no parent.)
