Need to document the thread-pool section in the ejb3 subsystem similar to EAP 6.4
But remove keepalive-time or make mention that it is not actually used or effective. As well as clarify max-threads is the max but also the core size, which means the thread pool will create a thread upon each request even if there are available threads until it reaches max and then remain there. As per: https://bugzilla.redhat.com/show_bug.cgi?id=1320680
So, the ejb3 subsystem defines a thread pool/pools, the thread pool is to specify how many threads are available for handing async ejbs running, ejb timers, and EJB calls that come in over the remoting subsystem. So if a remote call is made through the remote port, those requests are handled by the threads specified in the <remote ... thread-pool below. <subsystem xmlns="urn:jboss:domain:ejb3:4.0"> ... <async thread-pool-name="default"/> ... <timer-service thread-pool-name="default" default-data-store="default-file-store"> ... <remote connector-ref="http-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>
EAP 6.4: docs for reference
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
- is related to
-
JBEAP-3942 ejb3 subsystem thread-pools default config & xsd misleading
-
- Verified
-
-
-
- Closed
-
- relates to
-
-
- Closed
-
