You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2011/07/01 12:10:28 UTC
[jira] [Assigned] (CXF-3629) mbean WorkQueueManager misses
information about thread pool status
[ https://issues.apache.org/jira/browse/CXF-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang reassigned CXF-3629:
---------------------------------
Assignee: Freeman Fang
> mbean WorkQueueManager misses information about thread pool status
> ------------------------------------------------------------------
>
> Key: CXF-3629
> URL: https://issues.apache.org/jira/browse/CXF-3629
> Project: CXF
> Issue Type: Improvement
> Components: Core
> Reporter: Peter Repp
> Assignee: Freeman Fang
>
> WorkQueueManager can be used to monitor and adjust WorkQueue thread pool.
> The only parameters that can be changed are: High/Low WaterMark - concern thread numbers
> The only values showing *current* status concern queue size.
> Obviously Mbean misses information about current thread usage.
> Please add following methods to the class org.apache.cxf.workqueue.WorkQueueImplMBeanWrapper to allow observe thread usage also.
> @ManagedAttribute(description = "The largest number of threads")
> public int getLargestPoolSize() {
> return aWorkQueue.getLargestPoolSize();
> }
> @ManagedAttribute(description = "The current number of threads")
> public int getPoolSize() {
> return aWorkQueue.getPoolSize();
> }
> @ManagedAttribute(description = "The number of threads currently busy")
> public int getActiveCount() {
> return aWorkQueue.getActiveCount();
> }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira