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

[gunter zeilinger (JIRA)]

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

gunter zeilinger updated WFLY-10731:
------------------------------------
    Description: 
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 $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 )


  was:
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 $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}





> 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
>
> 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 $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.5.0#75005)