[jboss-jira] [JBoss JIRA] (WFCORE-553) ModelControllerClientOperationHandler doesn't manage the clientRequestExecutor properly
RH Bugzilla Integration (JIRA)
issues at jboss.org
Fri Mar 13 08:50:21 EDT 2015
[ https://issues.jboss.org/browse/WFCORE-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049836#comment-13049836 ]
RH Bugzilla Integration commented on WFCORE-553:
------------------------------------------------
baranowb <bbaranow at redhat.com> changed the Status of [bug 1199319|https://bugzilla.redhat.com/show_bug.cgi?id=1199319] from ASSIGNED to POST
> ModelControllerClientOperationHandler doesn't manage the clientRequestExecutor properly
> ----------------------------------------------------------------------------------------
>
> Key: WFCORE-553
> URL: https://issues.jboss.org/browse/WFCORE-553
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha18
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 1.0.0.Beta1
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
More information about the jboss-jira
mailing list