mina-dev mailing list archives

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

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

Goldstein Lyor commented on SSHD-715:

My view is that are a lot of collaborating components to achieve the complex SSH functionality.
Sometimes, there are interactions or inter-relations between them. The name {{IDLE_TIMEOUT}}
might not be fully indicative of its function, but it does show its function.

it makes IDLE_TIMEOUT useless, since it is impossible to set it to a value greater then the

I disagree - each value has its purpose (as previously indicate) and configuring a complex
system may sometime require non-trivial settings - especially if they interact with each other.

> 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

View raw message