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 Tue, 20 Dec 2016 17:41:58 GMT

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

Goldstein Lyor commented on SSHD-715:

I am not sure this would help - remember

* The user can modify these values on-the-fly, as well as make them session-scope only. We
do not have a mechanism that tracks all these changes (nor do I think it would be a good idea
to have one).
* Some values are read only once, or infrequently, so by the time they are used again (if
ever), the relationship between them which may have been OK is now wrong and warrants a warning,
but we won't know.
* There may be other such interr-related values, which would mean we have to "dirty" the code
with lots of parameters checks.

In view of this, I am not sure how effective such a change would be...

> 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