airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shameera Rathnayaka (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (AIRAVATA-1896) SSH connection timeouts not configured properly
Date Wed, 06 Apr 2016 18:50:25 GMT

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

Shameera Rathnayaka reassigned AIRAVATA-1896:
---------------------------------------------

    Assignee: Shameera Rathnayaka

> 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)

Mime
View raw message