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

Anudeep commented on SSHD-891:
------------------------------

Hi [~lgoldstein],

I would like to provide a brief note on the issue.

There is a client with ssh v2 version (omega) which is connecting to a server 
.In order to keep the session alive there is a mechanism from sever to send a 
message to client for every 30 seconds so that if there is not packet which 
needs to be send from server to client then a message would be sent to client 
for every 30 seconds.

The above scenario is able to withstand for one hour and immediately after one 
hour even though server sends a message to client ,it is not able to write and 
session is becoming idle for 10 mins .

Since ssh default idle timeout is 10 mins ssh server is killing the session.

So we need to understand why exactly after every one hour the message from 
server is not written.

It is not that easy for us now to migrate to latest version ,if we can find the 
root cause we will try to migrate.

 

Side effect of this issue is for every two days we are not able to open  a new 
ssh connection.

connections seems to be in CLOSE_WAIT state and no new connection is 
established.

 

Regards,

Anudeep

> SSh connections gets closed for every one hour with 0.13.0 version
> ------------------------------------------------------------------
>
>                 Key: SSHD-891
>                 URL: https://issues.apache.org/jira/browse/SSHD-891
>             Project: MINA SSHD
>          Issue Type: Bug
>            Reporter: Anudeep
>            Assignee: Goldstein Lyor
>            Priority: Blocker
>
> SSH connections are getting closed for every one hours after 10 mins of idle 
> time even though there are incoming pacets data is not being wriiten to 
> client for every one hour and is being idle(10 mins which is default timeout 
> of ssh session).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to