Details
-
Bug
-
Resolution: Done
-
Major
-
1.0.0.Alpha1, 1.0.0.Alpha18
-
None
Description
ModelControllerClientOperationHandler's constructor creates a ThreadPoolExecutor for handling client requests and then the class doesn't clean it up.
In addition, an instance of ModelControllerClientOperationHandler is created per channel, not one per ModelControllerClientOperationHandlerFactoryService. I know I at least thought of the thread pool as being per remote management interface, not per channel.
Making it be per ModelControllerClientOperationHandlerFactoryService and cleaning it up in that service's stop would be the easiest fix, but the pool settings may not be appropriate if we do that, so tread carefully.
Attachments
Issue Links
- is caused by
-
WFLY-3225 Rationalization of management thread pools
- Closed