[
https://issues.apache.org/jira/browse/AIRAVATA-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eroma closed AIRAVATA-2284.
---------------------------
tested and verified in
https://dev.seagrid.org
Currently the session duration is set to 30 minutes (this default value is set
internally in gfac i believe) If we want to change it has to be done in the
airavata properties file but this will effect all the gateways linked to the
particular airavata.
If a key changed, we need to advice the gateway admins to remain without
submitting jobs until the set session expires.
> Airavata session cacheing Creates issues for job submissions on remote
> clusters
> -------------------------------------------------------------------------------
>
> Key: AIRAVATA-2284
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2284
> Project: Airavata
> Issue Type: Bug
> Components: Airavata System, GFac
> Environment: GFAC
> Reporter: Eroma
> Assignee: Shameera Rathnayaka
> Fix For: 0.17
>
>
> Currently due to cacheing even when the keys are changed or removed till the
> jobs will get submitted as long as the session is open
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
