mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francesco Caliumi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SSHD-715) The IDLE_TIMEOUT configuration parameter is invalid
Date Wed, 07 Dec 2016 10:36:58 GMT

    [ https://issues.apache.org/jira/browse/SSHD-715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15728410#comment-15728410
] 

Francesco Caliumi commented on SSHD-715:
----------------------------------------

Hi [~lgoldstein],
I fell in the same trap. It may not be a bug in the proper sense of term, but is (in my opinion)
a failure to respect the contract of IDLE_TIMEOUT. In fact it makes IDLE_TIMEOUT useless,
since it is impossible to set it to a value greater then the default (that is probably the
need that can drive someone to set it in the first place).

For my curiosity, what need could lead to set NIO2_READ_TIMEOUT? (and specifically to set
it to a value lower then IDLE_TIMEOUT?)

Many thanks in advance,
Francesco.



> The IDLE_TIMEOUT configuration parameter is invalid
> ---------------------------------------------------
>
>                 Key: SSHD-715
>                 URL: https://issues.apache.org/jira/browse/SSHD-715
>             Project: MINA SSHD
>          Issue Type: Bug
>    Affects Versions: 1.3.0
>            Reporter: Li Fangning
>            Assignee: Goldstein Lyor
>            Priority: Minor
>             Fix For: 1.4.0
>
>
> The DEFAULT_IDLE_TIMEOUT value is set to 10 minutes.
> I want to configure it to never time out with the following code:
> PropertyResolverUtils.updateProperty(sshd, FactoryManager.IDLE_TIMEOUT, Long.MAX_VALUE);
> But the connection still times out after 10 minutes and 15 seconds.
> The problem can be circumvented by the following code:
> PropertyResolverUtils.updateProperty(sshd, FactoryManager.NIO2_READ_TIMEOUT, Long.MAX_VALUE);
> V1.2 does not have this problem.
> (The NIO2_READ_TIMEOUT parameter is new in version 1.3)
> The SSH client has the same problem.



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

Mime
View raw message