Hide Forgot
Description of problem: When configure a queueless-thread-pool or a blocking-queueless-thread-pool, EAP 6 server cannot shutdown. Version-Release number of selected component (if applicable): EAP 6.0 EAP 6.1 EAP 6.2 How reproducible: Always Steps to Reproduce: 1. Configure a queueless-thread-pool (or a blocking-queueless-thread-pool). ex) standalone.xml <subsystem xmlns="urn:jboss:domain:threads:1.1"> <queueless-thread-pool name="TestExecutor"> <max-threads count="1"/> </queueless-thread-pool> </subsystem> --- snip --- <subsystem xmlns="urn:jboss:domain:web:1.1" default-virtual-server="default-host" native="false"> <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" executor="TestExecutor"/> 2. Run EAP server. 3. Shutdown EAP server. 4. Does not end shutdown process.
For given setting the process of EAP 6.3.0.ER10 server still does not end after the server shutdown.
This executor configuration looks obviously broken (same as 882048). I don't see a real way to handle this.
FYI, I've tried to reproduced the issue, with the given configuration, and JBoss EAP-6.4.0.DR13 (using both OracleJDK and OpenJDK) on my Linux (Fedora 21) without any success at reproducing the issue. So either my local env is somehow "wrong" (and it could be), or either the issue appears to be resolved...
No idea, but the executor is a black box, it is not possible to check if the configuration is appropriate but as I could see there's a nice amount of creativity in that area. Bad configurations will make the connector misbehave especially things like: - Having one thread because it is cool (solution: have a reasonable amount of threads instead) - Block in any way since the connector will stop doing anything during that time, the executor behavior should be to either give a thread or refuse the execution
I have reproduced the issue with old version of EAP and verified, that it is fixed since EAP 6.4.0.DR8. I don't know what change fixed it, probably some update in Threads subsystem as between EAP 6.4.0.DR7 and EAP 6.4.0.DR8 the version of org.jboss.threads changed from 2.1.1.Final-redhat-1 to 2.1.2.Final As the issue is no longer valid, setting as verified.