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

Posted to issues@airavata.apache.org by "Shameera Rathnayaka (JIRA)" <ji...@apache.org> on 2016/07/11 22:01:11 UTC

[jira] [Resolved] (AIRAVATA-1896) SSH connection timeouts not configured properly

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

Shameera Rathnayaka resolved AIRAVATA-1896.
-------------------------------------------
    Resolution: Fixed

> SSH connection timeouts not configured properly
> -----------------------------------------------
>
>                 Key: AIRAVATA-1896
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1896
>             Project: Airavata
>          Issue Type: Bug
>          Components: GFac
>            Reporter: Marlon Pierce
>            Assignee: Shameera Rathnayaka
>             Fix For: 0.16
>
>
> We noticed this after a slow SSH connection to submit jobs to Comet. JSCH property settings should have set the timeout to 360000 milliseconds (6 minutes), which is much longer than even the delayed timeout.  Comet delays were maybe ~30-60 seconds.
> JSCH's default connection time out is 20 seconds, so it is possible that the default value is being used and not overwritten correctly. 



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