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. Version-Release number of selected component (if applicable): 6.x
Complementing information to this bugzilla: "the desired functionality is to, when a new request arrives and there is an idle thread, use that thread instead of creating a new thread [up until max-threads]."
Jira PRODMGT-1401 created to address the new requirement customer is asking for -------------------- "the desired functionality is to, when a new request arrives and there is an idle thread, use that thread instead of creating a new thread [up until max-threads]." -------------------- as well as including the info. in WFLY-5332
The creation of a new ThreadPoolExecutor is required.
This is an RFE not a but, the RFE for it is : PRODMGT-1401 , closing the bz as the rfe will be handled via PRODMGT-1401