[
https://issues.jboss.org/browse/AS7-5448?page=com.atlassian.jira.plugin.s...
]
Mathieu Lachance commented on AS7-5448:
---------------------------------------
Sorry for the misunderstanding, yes I was referring to the threads subsystem.
as defined in the jboss-threads-2.0.0.GA.jar packaged in the jboss 7.1.2.Final
distribution
org.jboss.threads.JBossThreadPoolExecutor implements
org.jboss.threads.management.ThreadExecutorMBean, I think the getQueueSize() method should
be added here.
org.jboss.threads.JBossThreadPoolExecutor extends java.util.concurrent.ThreadPoolExecutor,
so the BlockingQueue I was talking about is available, making the getQueueSize() method a
snap to implements.
should the issue be filled instead in the jboss-threads jira ?
expose thread pool queue size through jmx
-----------------------------------------
Key: AS7-5448
URL:
https://issues.jboss.org/browse/AS7-5448
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.2.Final (EAP)
Reporter: Mathieu Lachance
Assignee: Stuart Douglas
issue
https://issues.jboss.org/browse/AS7-793 is not completed.
thread pool exposed in jmx is still missing the queue size which is an essential metric
to evaluate the system load.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira