[jboss-jira] [JBoss JIRA] (WFLY-8966) EJB subsystem thread-pool statistics largest-thread-count is counting threads instead of show the peak of parallel use

[Petr Jurak (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-8966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Petr Jurak resolved WFLY-8966.
------------------------------
    Resolution: Won't Fix


Not a bug. It shows exactly the largest number of threads in the pool. The reason it ends up with the value equal to max pool size is that core threads count is equal to max pool size for this executor. And core threads will not expire.

> EJB subsystem thread-pool statistics largest-thread-count is counting threads instead of show the peak of parallel use
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-8966
>                 URL: https://issues.jboss.org/browse/WFLY-8966
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 11.0.0.CR1
>            Reporter: Wolf-Dieter Fink
>            Assignee: Petr Jurak
>         Attachments: ejb31-timer.jar
>
>
> The description of "largest-thread-count" is 
>  => "The largest number of threads that have ever simultaneously been in the pool."
> But the behaviour at runtime shows that it is handled similar to task-count.
> If only one thread is used it will increased for every invocation until max-threads.
> As result the largest-thread-count is == max-threads after a short time.
> The helpful metrict to check whether the threads are exhaused is missing!



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)