To test monitoring JMX MBeans run JConsole (type "jconsole" in the command line) and attach to the process of application server to which the sample is deployed. If you use Jetty (default option), then connect to the process which has jetty in the name (e.g. "org.codehaus.plexus.classworlds.launcher.Launcher jetty:run"). Then open tab MBeans and look for org.glassfish.jersey group. There you can find MBeans with statistics information about the deployed application. Go to for example to Uris/resource/MethodTimes/attribues.

Make some requests to the deployed application in order to modify statistics. These are available URIs:

## Root resource

URI | HTTP Method | Consumes / Produces | Description
--- | --- | --- | ---
rest/resource | GET | */* | Simple GET resource
rest/resource | POST | */* | Simple POST resource
rest/resource/sub | GET | */* | GET resource that takes random time to process (500...1500 ms)
rest/resource/sub2 | POST | Consumes: text/plain; Produces: text/html | Simple POST resource
rest/resource/exception | GET | */* | Throws exception which is mapped by the exception mapper (modifies exception statistics under Global/ExceptionMapper)
rest/resource/locator | GET |  | Sub resource locator that returns SubResource (see below)

## SubResource

URI | HTTP Method | Consumes / Produces | Description
--- | --- | --- | ---
.../in-subresource (e.g. rest/resource/locator/in-subresource) | GET | */* | Simple GET resource (MBean will be added once you reach this URI).
.../locator (e.g. rest/resource/locator/locator/locator/in-subresource | GET |  | Sub resource locator that recursively returns this SubResource (you can call recursively locator many times using this method and always new URI will be added to statistics)