[jboss-jira] [JBoss JIRA] (WFLY-6321) Create tool to monitor clustering thread pool usage

[Richard Achmatowicz (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-6321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172245#comment-13172245 ] 

Richard Achmatowicz edited comment on WFLY-6321 at 3/4/16 1:57 PM:
-------------------------------------------------------------------

The tool is based on Byteman. Here are the ingredients:

1. A set of Byteman rules which get triggered when thread pools are created and accessed (in the case of count based monitoring) OR a set of rules which get triggered every 10 seconds (in the case of period based monitoring)  
2. a JBoss Modules module called org.wildfly.byteman.rule.helper.threadpool which contains several Byteman helper classes which are made use of by the rules (see https://github.com/rachmatowicz/byteman-threadpool-helper) 
3. A SmartFrog job configured to test a custom build, start Byteman with the rule sets on each server and post-process the server logs to extract the thread pool statistics generated and present them in a separate report
   
The build under test currently needs to have the org.wildfly.byteman.rule.helper.threadpool module added to it in order for the Byteman rules to work. This has to do with reconciling JBoss Modules classloading with the way Byteman works by default (in non-application server contexts).


was (Author: rachmato):
The tool is based on Byteman. Here are the ingredients:

1. A set of Byteman rules which get triggered when thread pools are created and accessed (in the case of count based monitoring) OR a set of rules which get triggered every 10 seconds (in the case of period based monitoring)  
2. a JBoss Modules module called org.wildfly.byteman.rule.helper.threadpool which contains several Byteman helper classes which are made use of by the rules (see https://github.com/rachmatowicz/byteman-threadpool-helper) 
3. A SmartFrog job configured to test a custom build, start Byteman with the rule sets on each server and post-process the server logs to extract the thread pool statistics generated and present them in a separate report
   


> Create tool to monitor clustering thread pool usage
> ---------------------------------------------------
>
>                 Key: WFLY-6321
>                 URL: https://issues.jboss.org/browse/WFLY-6321
>             Project: WildFly
>          Issue Type: Task
>          Components: Clustering
>            Reporter: Richard Achmatowicz
>            Assignee: Richard Achmatowicz
>            Priority: Minor
>
> Scheduled executors and thread pools are used widely in JGroups and Infinispan for asynchronously executing tasks.  When thread pools are not adequately sized to the load they are subjected to, this can lead to performance problems. 
> It would be helpful if we could see thread pool usage as a function of elapse time during performance runs, in order to diagnose potential thread pool issues.
> This task will provide a Byteman-based tool to monitor threadpool usage and allow a report to be attached to SmartFrog test jobs.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)