Get rid of the clientRequestExecutor in AbstractModelControllerOperationHandlerFactoryService --------------------------------------------------------------------------------------------- Key: WFCORE-2282 URL: https://issues.jboss.org/browse/WFCORE-2282 Project: WildFly Core Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Fix For: 5.0.0.Alpha1 AbstractModelControllerOperationHandlerFactoryService creates a thread pool for handling management requests, with the goal being to limit the number of concurrently executing requests to 4, with tasks for other requests being queued. There are other ways to do this kind of limitation that do not involve a new thread pool. See Undertow's RequestLimitHandler and related RequestLimit class for the template. This task is to implement the equivalent in org.jboss.as.controller.remote (not as public API) and then switch the execution to the ServerService Thread Pool (on a server) or the HostControllerService Thread Pool (on an HC). It is *not* a request to move execution to the XNIO worker task thread. That should not be done without a very clear discussion. Part of this task is to account for the thinking that went into a fix for WFCORE-1529. IOW moving work to ServerService Thread Pool / HostControllerService Thread Pool will likely affect the optimum core sizes of those pools. This AbstractModelControllerOperationHandlerFactoryService.clientRequestExecutor is what is referred to in the PR for WFCORE-1529 in its discussion of "management-handler-thread".