[
https://issues.apache.org/jira/browse/DIRMINA-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918473#action_12918473
]
Patrick Peck commented on DIRMINA-802:
--------------------------------------
Sorry, but the SocketConnector is buried somewhere deep in our project, and the
SocketConnector API changed significantly between 1.0.7 and 2.0.0. In addition
to that, the compile/build/test cycle of our project is quite time consuming so
in the short term I see no chance of providing you with that info.
> 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.
