[jira] Resolved: (DIRMINA-802) SocketConnector uses non-daemon thread

["Emmanuel Lecharny (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DIRMINA-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny resolved DIRMINA-802.
---------------------------------------

    Resolution: Won't Fix

AFAICT, this is the expected behavior. In 2.0, if you call the NioSocketConnector(), it creates an internal Executor pool. If you want control on this executor pool, you can still create it before calling the constructor.

> SocketConnector uses non-daemon thread
> --------------------------------------
>
>                 Key: DIRMINA-802
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-802
>             Project: MINA
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 1.1.7
>            Reporter: Patrick Peck
>            Priority: Minor
>
> The no-args constructor of the class org.apache.mina.transport.socket.nio.SocketConnector uses a NewThreadExecutor for handling background processing tasks.
> The problem is, that NewThreadExecutor starts a non-daemon thread. This causes problems when the class is used in Tomcat, because the server refuses to shut down and can only be stopped using a process kill.
> In my environment, I have fixed the problem by explicitly calling the SocketConnector(int processorCount, Executor executor) constructor and providing an executor that starts a daemon thread.
> IMHO, this should be the default behaviour.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.