[
https://issues.apache.org/jira/browse/DIRMINA-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16222219#comment-16222219
]
Jonathan Valliere commented on DIRMINA-1060:
--------------------------------------------
Correct, its a work around. There is no practical way of preventing the
spinning without the {{thread.sleep}}. This method allows the currently
connected sockets to continue to operate normally until new sockets can be
accepted otherwise the {{Acceptor}} will spin as fast as possible and eat an
entire core. If you had 2-3 {{Acceptors}} and 4 cores, that might be a problem.
I thought that condition was the basis for this bug. I thought there was some
mention of unlimit spinning in the mailing list a while back and put the two
together.
> Handle the spinning selectors in Socket/Datagram Acceptor and Connector
> -----------------------------------------------------------------------
>
> Key: DIRMINA-1060
> URL: https://issues.apache.org/jira/browse/DIRMINA-1060
> Project: MINA
> Issue Type: Bug
> Affects Versions: 2.0.16
> Reporter: Emmanuel Lecharny
> Fix For: 2.0.17
>
>
> We have a workaround for the selector spinning issue in NioProcessor, we need
> to use it for the Acceptor/Connector Datagram/Socket implementation
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
