[jboss-jira] [JBoss JIRA] (JGRP-2196) TP: internal thread pool is not shut down

Bela Ban (JIRA) issues at jboss.org
Wed Jun 21 07:38:00 EDT 2017


     [ https://issues.jboss.org/browse/JGRP-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bela Ban updated JGRP-2196:
---------------------------
    Description: 
In {{TP.destroy()}}, the regular thread pool and timer are shut down, but not the internal thread pool. The result is that sometimes closing a channel takes a longer time (the max idle time for a thread in the pool). This only happens when an internal thread is active at the time of shut down.

Also use a separate thread factory for internal threads, so we can see by the naming whether a thread is regular or internal, e.g. "jgroups-23" (regular) versus "jgroups-int-33"

  was:
In {{TP.destroy()}}, the regular thread pool and timer are shut down, but not the intrnal thread pool.

Also use a separate thread factory for internal threads, so we can see by the naming whether a thread is regular or internal, e.g. "jgroups-23" (regular) versus "jgroups-int-33"



> TP: internal thread pool is not shut down
> -----------------------------------------
>
>                 Key: JGRP-2196
>                 URL: https://issues.jboss.org/browse/JGRP-2196
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 4.0.4
>
>
> In {{TP.destroy()}}, the regular thread pool and timer are shut down, but not the internal thread pool. The result is that sometimes closing a channel takes a longer time (the max idle time for a thread in the pool). This only happens when an internal thread is active at the time of shut down.
> Also use a separate thread factory for internal threads, so we can see by the naming whether a thread is regular or internal, e.g. "jgroups-23" (regular) versus "jgroups-int-33"



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jboss-jira mailing list