[jboss-jira] [JBoss JIRA] (WFCORE-1341) Expose IO worker runtime data / statistics

[Tomaz Cerar (JIRA)]

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

Tomaz Cerar commented on WFCORE-1341:
-------------------------------------

Example of output with current proposed impl in PR https://github.com/wildfly/wildfly-core/pull/1990

{noformat}
[standalone at localhost:9990 /] /subsystem=io/worker=default:read-resource(recursive=true, include-runtime=true)
{
    "outcome" => "success",
    "result" => {
        "core-pool-size" => 4,
        "io-thread-count" => 16,
        "io-threads" => undefined,
        "max-pool-size" => 128,
        "queue-size" => 0,
        "shutdown-requested" => false,
        "stack-size" => 0L,
        "task-keepalive" => 60,
        "task-max-threads" => undefined,
        "server" => {
            "/127.0.0.1:8080" => {
                "connection-count" => -1,
                "connection-limit-high-water-mark" => 2147483647,
                "connection-limit-low-water-mark" => 2147483647
            },
            "/127.0.0.1:8443" => {
                "connection-count" => -1,
                "connection-limit-high-water-mark" => 2147483647,
                "connection-limit-low-water-mark" => 2147483647
            }
        }
    }
}
{noformat}

> Expose IO worker runtime data / statistics
> ------------------------------------------
>
>                 Key: WFCORE-1341
>                 URL: https://issues.jboss.org/browse/WFCORE-1341
>             Project: WildFly Core
>          Issue Type: Enhancement
>          Components: Remoting
>    Affects Versions: 2.0.7.Final
>            Reporter: Brad Maxwell
>            Assignee: Tomaz Cerar
>
> The remoting subsystem uses a worker-thread-pool which can be configured such as shown below.
> The runtime thread pool information is not exposed when doing read-resource:
> {code}
> /subsystem=remoting:read-resource(include-runtime=true, recursive=true)
> {code}
> {code}
> <subsystem xmlns="urn:jboss:domain:remoting:1.1">
>    <worker-thread-pool
>        read-threads="1"
>        task-core-threads="4"
>        task-keepalive="60"
>        task-limit="16384"
>        task-max-threads="16"
>        write-threads="1"
>     />
>     <connector name="remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/>
> </subsystem>
> {code}
> In tuning and runtime diagnosis, it would be useful to see the thread pool information such as the current size, queue-size, largest-thread-count, etc similar to the ejb3 subsystem thread pool: 
> {code}
> /subsystem=ejb3/thread-pool=default:read-resource(include-runtime=true, recursive=true)
>     "result" => {
>         "active-count" => 0,
>         "completed-task-count" => 0L,
>         "current-thread-count" => 0,
>         "keepalive-time" => {
>             "time" => 100L,
>             "unit" => "MILLISECONDS"
>         },
>         "largest-thread-count" => 0,
>         "max-threads" => 10,
>         "name" => "default",
>         "queue-size" => 0,
>         "rejected-count" => 0,
>         "task-count" => 0L,
>         "thread-factory" => undefined
>     }
> {code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)