Description of problem: Create an unbounded queueless executor ${quote} <unbounded-queue-thread-pool name="uq-thread-pool"> <max-threads count="350"/> <keepalive-time time="5" unit="minutes"/> </unbounded-queue-thread-pool> ${quote} Modifying max-threads fails: ${quote} /subsystem=threads/unbounded-queue-thread-pool=uq-thread-pool:write-attribute(name=max-threads,value=300) { "outcome" => "failed", "failure-description" => "JBAS014749: Operation handler failed: null", "rolled-back" => true } ${quote} ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("write-attribute") failed - address: ([ ("subsystem" => "threads"), ("unbounded-queue-thread-pool" => "uq-thread-pool") ]): java.lang.IllegalArgumentException at java.util.concurrent.ThreadPoolExecutor.setMaximumPoolSize(ThreadPoolExecutor.java:1620) [rt.jar:1.7.0] at org.jboss.threads.JBossThreadPoolExecutor.setMaxThreads(JBossThreadPoolExecutor.java:95) [jboss-threads-2.1.1.Final.jar:2.1.1.Final] at org.jboss.as.threads.ManagedJBossThreadPoolExecutorService.setMaxThreads(ManagedJBossThreadPoolExecutorService.java:86) at org.jboss.as.threads.UnboundedQueueThreadPoolService.setMaxThreads(UnboundedQueueThreadPoolService.java:91) The core pool size needs to be adjusted in line with the max pool size and in the right order to avoid that since max threads can't be less than core threads. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Aaron Ogburn <aogburn> made a comment on jira WFLY-2336 Merged now upstream so this can be closed.
Aaron Ogburn <aogburn> updated the status of jira WFLY-2336 to Resolved
PR: https://github.com/jbossas/jboss-eap/pull/636
I don't know who the QE contact should, be, but as it was acked, it's now merged.
Verified with EAP 6.2.0.CR1.