[jboss-jira] [JBoss JIRA] (WFCORE-1446) EJB thread pool keepalive not honored and is not reusing inactive threads

[Brad Maxwell (JIRA)]

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

Brad Maxwell moved JBEAP-3913 to WFCORE-1446:
---------------------------------------------

              Project: WildFly Core  (was: JBoss Enterprise Application Platform)
                  Key: WFCORE-1446  (was: JBEAP-3913)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s:     (was: EJB)
       Target Release:   (was: 7.backlog.GA)
    Affects Version/s:     (was: 7.0.0.ER5)


> EJB thread pool keepalive not honored and is not reusing inactive threads
> -------------------------------------------------------------------------
>
>                 Key: WFCORE-1446
>                 URL: https://issues.jboss.org/browse/WFCORE-1446
>             Project: WildFly Core
>          Issue Type: Bug
>            Reporter: Brad Maxwell
>            Assignee: Panagiotis Sotiropoulos
>
> Copied description from BZ1255494 : 
> Description of problem:
> It looks like the ejb3 subsystem thread pool configuration is hard coded to create an unbounded thread pool, where it it looks like max-threads = core-threads, and thus the threads will increase up to the max-threads configured and then remain there.  The keep-alive setting which appears in many of the docs & default configurations is ineffective since max=core.
> ejb3/src/main/java/org/jboss/as/ejb3/subsystem/EJB3SubsystemRootResourceDefinition.java
> I tried defining a different thread pool in the threads subsystem and tried to reference it from the ejb3 subsystem, however it looks like the ejb3 subsystem only looks for thread pools configured in the ejb3 subsystem.



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