[
https://issues.apache.org/jira/browse/DIRMINA-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944184#comment-14944184
]
Emmanuel Lecharny commented on DIRMINA-1015:
--------------------------------------------
OTOH, as we provide a way for you to create your own Execurot, nothing forbid
you to pass the ThreadFactory that creates daemon threads if needed.
> AbstractIoService creates unnamed non-daemon threads
> ----------------------------------------------------
>
> Key: DIRMINA-1015
> URL: https://issues.apache.org/jira/browse/DIRMINA-1015
> Project: MINA
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0.9
> Reporter: Matt Kusnierz
> Priority: Minor
>
> The org.apache.mina.core.service.AbstractIoService can create an executor in
> its constructor. This executor is creating simply using the
> java.util.concurrent.Executors.newCachedThreadPool() factory method. But this
> create threads with unhelpful "thread-x-pool-y" names, and more importantly
> creates non-daemon threads. The daemon thread aspect can lead to applications
> not properly terminating. When no executor is supplied as a constructor
> argument, the default should be to create a newCachedThreadPool, but to
> supply a ThreadFactory that a) creates "mina-xxx" named threads, and b)
> creates daemon threads.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
