Date: Tue, 10 Mar 2015 17:26:28 +0000
Hi
We are performing Stability load run against our Grizzly based application.
We are trying to determine how to monitor the Thread Pool usage via JMX.
We are looking at the ThreadPool MBean (org.glassfish.grizzly:pp=/gmbal-root/TCPNIOTransport[EndPoint.IMAP.NON_SECURED],type=ThreadPool,name=ThreadPool), on the following attributes:
* thread-pool-max-num-threads
* thread-pool-allocated-thread-count
* thread-pool-core-pool-size
We have conducted 2 load runs (with exactly the same load model):
1. max threads was configured to be 200 (verified against thread-pool-max-num-threads)
o from some point of the load run the thread-pool-allocated-thread-count was stabilized on 188
o thread-pool-core-pool-size was fixed on 12
2. max threads was configured to be 300 (verified against thread-pool-max-num-threads)
o from some point of the load run the thread-pool-allocated-thread-count was stabilized on 288
o thread-pool-core-pool-size was fixed on 12
The questions are as follows:
1. Are we looking on the right MBean attributes?
2. Assuming 1 is true, then why for the same load model the thread pool is reaching this high number (max = core + allocated)?
3. Why the thread-pool-started attribute is false?
Attaching the JConsole print screen of the second run
[cid:image001.png_at_01D05B52.9D7A53B0]
Thanks
Uri
________________________________
"This e-mail message may contain confidential, commercial or privileged information that constitutes proprietary information of Comverse Inc. or its subsidiaries. If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies and contact us by e-mailing to: security_at_comverse.com. Thank You."
(image/png attachment: image001.png)