[jboss-jira] [JBoss JIRA] (JGRP-2246) Internal thread pool not created if default thread pool is injected

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13522970#comment-13522970 ] 

Bela Ban edited comment on JGRP-2246 at 1/24/18 6:36 AM:
---------------------------------------------------------

I added method {{setInternalThreadPool()}} in JGRP-2244. I assume this resolved your issue?

And, no, I don't want to create the internal thread pool is {{thread_pool_enabled}} is {{false}}, as this attribute governs the creation of both pools.


was (Author: belaban):
I added method {{setInternalThreadPool()}} in JGRP-2244. I assume this resolved your issue?

> Internal thread pool not created if default thread pool is injected
> -------------------------------------------------------------------
>
>                 Key: JGRP-2246
>                 URL: https://issues.jboss.org/browse/JGRP-2246
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 4.0.9
>            Reporter: Paul Ferraro
>            Assignee: Bela Ban
>             Fix For: 4.0.10
>
>
> WildFly injects a custom thread pool into its JGroups transports.
> However, in JGroups 4.0.x, only the default thread pool exposes a {{setThreadPool(...)}} method.  The internal thread pool does not.  However, the logic within {{TP.init()}} will not create an internal thread pool if the default thread pool already exists (and is not shutdown), which is the case in WildFly.
> Can we restore the {{TP.setInternalThreadPool(...)}} method?  Alternatively, assuming JGRP-2244 is fixed, can we fix this logic such that the internal thread pool is always created when {{thread_pool_enabled}} is true? 



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)