From: Ryan Lubke <ryan.lubke_at_oracle.com>
Date: Mon, 15 Oct 2012 11:51:51 -0700

If you obtain the NetworkListener(s) associated with your HttpServer
instance, you can, from said NetworkListener, get the associated
Transport and query the two different thread pool implementations.
Additionally, you can add probes to the thread pools so that you can
monitor when threads are created, etc. (probably more useful when not
using a fixed thread pool).

See [1], [2], and [3]

[1]
http://grizzly.java.net/nonav/docs/docbkx2.2/html/core-config.html#transport-config
[2]
http://grizzly.java.net/nonav/docs/docbkx2.2/html/core-config.html#threadpool-config
[3]
http://grizzly.java.net/nonav/docs/docbkx2.2/html/monitoring.html#monitoring-core

> myxjtu_at_yahoo.com <mailto:myxjtu_at_yahoo.com>
> October 13, 2012 8:28 PM
> I am doing some async web service experiments using Jersey 2.X and
> Grizzly 2.x. So I like to check the number of threads allocated by
> Grizzly server. Is there an API to do that? Thanks!