[
https://issues.apache.org/jira/browse/AIRAVATA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657590#comment-15657590
]
ASF subversion and git services commented on AIRAVATA-2212:
-----------------------------------------------------------
Commit 3910260e58b3e1c5c554bada3dd33ded9e7fd403 in airavata-php-gateway's
branch refs/heads/develop from [~marcuschristie]
[ https://git-wip-us.apache.org/repos/asf?p=airavata-php-gateway.git;h=3910260 ]
AIRAVATA-2212 Using setInterval so status check is turned back on
The way it was implemented with setTimeout the status checking
(autoRefresh) wouldn't start again once it was toggled back on. I
switched to setInterval since it is easier to just check the autoRefresh
flag every 3 seconds.
> Experiment Auto Refresh may try to reload the page while reloading the page
> ---------------------------------------------------------------------------
>
> Key: AIRAVATA-2212
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2212
> Project: Airavata
> Issue Type: Bug
> Reporter: Marcus Christie
> Assignee: Marcus Christie
>
> The Experiment Auto Refresh feature has a bug that occurs when it takes more
> than about 3 seconds to load the experiment summary. Experiment Auto Refresh
> runs an Ajax request every 3 seconds to check to see if the experiment status
> has changed. If the experiment status has changed it tries to reload the
> page. However, it keeps checking every 3 seconds and it is possible for the
> summary page to
> * check to see if the experiment status has changed
> * start reloading the page
> * check a second time to see if the experiment status has changed
> * start reloading the page a second time
> * etc.
> For [~eroma_a] the summary page basically got stuck in this loop and never
> refreshed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
