[
https://issues.apache.org/jira/browse/DIRMINA-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRMINA-668.
---------------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 3.0.0-M3)
2.0.8
There are ways to handle such a situation either by using an executor filter,
or by dealing with costly operations on the IoHandler
> Modify the way we use IoProcessors
> ----------------------------------
>
> Key: DIRMINA-668
> URL: https://issues.apache.org/jira/browse/DIRMINA-668
> Project: MINA
> Issue Type: Improvement
> Affects Versions: 2.0.0-M4
> Reporter: Emmanuel Lecharny
> Fix For: 2.0.8
>
>
> In the current code base, when accepting new connections, we pick a processor
> and register the news connection within the internal selector. In other
> words, we have as many selectors as we have IoProcessors.
> This is a potential problem if some request cost a lot to be executed, as
> every requests waiting on this IoProcessor will be blocked.
> It would be way better to use a single selector which dispatches requests to
> an Executor, as we will always have available threads ready to process the
> requests (unless the pool is saturated, but then we have a bigger issue ...)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
