You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Amol Nayak (JIRA)" <ji...@apache.org> on 2011/01/02 15:28:45 UTC
[jira] Updated: (DIRMINA-814) Slow Receivers(servers) cannot read
data already written by client applications after connection close is
initiated by client
[ https://issues.apache.org/jira/browse/DIRMINA-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amol Nayak updated DIRMINA-814:
-------------------------------
Summary: Slow Receivers(servers) cannot read data already written by client applications after connection close is initiated by client (was: Slow Receivers cannot read already read data by client connection close initiated by client)
> Slow Receivers(servers) cannot read data already written by client applications after connection close is initiated by client
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: DIRMINA-814
> URL: https://issues.apache.org/jira/browse/DIRMINA-814
> Project: MINA
> Issue Type: Bug
> Components: Core
> Environment: Windows Vista
> Reporter: Amol Nayak
> Fix For: 2.0.3
>
> Attachments: Mina20Server.java, SimpleMINAServerClient.java, Toronto.txt
>
>
> A simple MINA server is developed which is simulating a slow server, the read is done after a sleep of 10 ms.
> A clients writes a huge chunk of bytes and closes the connection.
> This close denies a read to the stream from the client and the data already sent to server is not available for read.
> A more reasonable behavior is to disallow writes but allow the server to read at least what is being already published to the server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.