You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mina.apache.org by "Goldstein Lyor (JIRA)" <ji...@apache.org> on 2016/02/20 11:25:18 UTC

[jira] [Assigned] (SSHD-651) Add an option to specify read/write Nio2 socket timeouts

     [ https://issues.apache.org/jira/browse/SSHD-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Goldstein Lyor reassigned SSHD-651:
-----------------------------------

    Assignee: Goldstein Lyor

> Add an option to specify read/write Nio2 socket timeouts
> --------------------------------------------------------
>
>                 Key: SSHD-651
>                 URL: https://issues.apache.org/jira/browse/SSHD-651
>             Project: MINA SSHD
>          Issue Type: Bug
>    Affects Versions: 1.1.0
>            Reporter: Eugene Petrenko
>            Assignee: Goldstein Lyor
>
> Currently, as I see from Nio2Acceptor and Nio2Session code we call socket async read/write without specifying ant timeouts. This may mean that for some cases this read/write may stuck eternally. 
> Currently I see such dangling connections on my application. 
> It could be nice if we were ably to pass some fixed timeout for low-level socket operations. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)