[jboss-jira] [JBoss JIRA] (WFLY-10731) core-threads of ManagedScheduledExecutorService limits number of maximal threads

[Jiri Ondrusek (Jira)]

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

Jiri Ondrusek commented on WFLY-10731:
--------------------------------------

Behavior of server is correct, property "core-threads" should limit min and also max number.

It's probable that misunderstanding was caused by bad description from [1] - {quote}core-threads The minimum number of threads to be used by the scheduled executor{quote}.
But correct meaning of attribute is (e.g. from [2]): {quote}The mandatory core-threads provides the number of threads to keep in the executor's pool, even if they are idle. A value of 0 means there is no limit.{quote} 

But there was also a smaller error - there was missing implementation of "A value of 0 means there is no limit". It was added by PR.


[1] https://wildscribe.github.io/WildFly/14.0/subsystem/ee/managed-scheduled-executor-service/index.html
[2] https://docs.jboss.org/author/display/WFLY10/EE+Concurrency+Utilities+Configuration

> core-threads of ManagedScheduledExecutorService limits number of maximal threads
> --------------------------------------------------------------------------------
>
>                 Key: WFLY-10731
>                 URL: https://issues.jboss.org/browse/WFLY-10731
>             Project: WildFly
>          Issue Type: Bug
>          Components: EE
>    Affects Versions: 12.0.0.Final
>            Reporter: gunter zeilinger
>            Assignee: Jiri Ondrusek
>            Priority: Major
>
> After changing the default configuration:
> {noformat}
>                  <managed-scheduled-executor-services>
> -                    <managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" hung-task-threshold="60000" keepalive-time="3000"/>
> +                    <managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" long-running-tasks="true" core-threads="2" keepalive-time="3000"/>
>                  </managed-scheduled-executor-services>
> {noformat}
> only 2 (= value of core-threads) threads are used by the Scheduled Executer Service:
> {code:bash}
> $ grep ManagedScheduledExecutorService $WILDFLY/standalone/log/server.log | tail
> 2018-07-24 12:03:22,901 INFO  [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) ..
> 2018-07-24 12:03:22,911 INFO  [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) ..
> 2018-07-24 12:03:22,923 INFO  [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) ..
> 2018-07-24 12:03:22,963 INFO  [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) ..
> 2018-07-24 12:03:22,967 INFO  [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) ..
> 2018-07-24 12:03:22,981 INFO  [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) ..
> 2018-07-24 12:03:22,996 INFO  [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) ..
> 2018-07-24 12:03:23,016 INFO  [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) ..
> 2018-07-24 12:03:23,035 INFO  [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) ..
> 2018-07-24 12:03:23,039 INFO  [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) ..
> {code}
> I have not yet tested if the issue also effects Wildfly 13.0.0.Final ( cannot use Wildfly 13.0.0.Final because of WFLY-10531 )



--
This message was sent by Atlassian Jira
(v7.12.1#712002)