You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Mike Heath (JIRA)" <ji...@apache.org> on 2008/03/07 04:28:59 UTC
[jira] Closed: (DIRMINA-461) Possible TCP stall consideration
[ https://issues.apache.org/jira/browse/DIRMINA-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Heath closed DIRMINA-461.
------------------------------
Resolution: Fixed
There has been no report of TCP stall in MINA so I'm closing this issue. If anyone actually experiences TCP stall, please re-open.
> Possible TCP stall consideration
> --------------------------------
>
> Key: DIRMINA-461
> URL: https://issues.apache.org/jira/browse/DIRMINA-461
> Project: MINA
> Issue Type: Improvement
> Components: Core
> Reporter: immars
>
> Hello,
> There is a Mr. Michael T. Nygard explaining a TCP stall problem he met when dealing with java NIO:
> http://www.highscalability.com/comment/reply/168/360
> The main idea is to read as much data as possible when a channel is selected as readable to minimize the data cumulation in this socket's TCP buffer during thread scheduling.
> I haven't reproduced or verified this issue yet, however, I wonder is it a potential threat to MINA as well?
> Thanks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.