Hide Forgot
Document URL: https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#sect-Configuring_EJB_Thread_Pools <subsystem xmlns="urn:jboss:domain:ejb3:1.5"> ... <async thread-pool-name="default"/> <timer-service thread-pool-name="default" default-data-store="default-file-store"> ... <remote connector-ref="remoting-connector" thread-pool-name="default"/> <thread-pools> <thread-pool name="default"> <max-threads count="10"/> <keepalive-time time="100" unit="milliseconds"/> </thread-pool> </thread-pools> ... </subsystem> Section Number and Name: Describe the issue: keepalive-time should be removed as it is not actually used, as the thread pool created sets core threads = max threads, thus the max-threads is the max # of threads but effectively the # of threads, meaning the threads pool will create threads a thread on every request until it reaches max and then remain there. Even if there is only 1 concurrent client such that there are free threads in the pool, it will still create them until hitting max. Suggestions for improvement: Additional information:
Romain Pelisse <belaran> updated the status of jira JBEAP-3943 to Coding In Progress
David Michael <dmichael> updated the status of jira JBEAP-3943 to Coding In Progress
Martin Simka <msimka> updated the status of jira JBEAP-3943 to Reopened
This topic needed more cleanup. The keep-alive element was commented out instead of being removed and was still appearing in the rendered documentation. Also, other references to 'keep-alive' needed to be removed.
Verified here: https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#sect-Configuring_EJB_Thread_Pools Revision 6.4.0-45 Thursday September 22 2016