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

Marcus Christie updated AIRAVATA-2376:
--------------------------------------
    Description: When experiments are launched there are two records in 
EXPERIMENT SUMMARY table for LAUNCHED and EXECUTING state which has the exact 
same state change time. In PGA however two records show up for the same 
experiment and with same status. e.g.: two exact records for a single 
experiment. This only appears until the experiment is FAILED or COMPLETED. But 
both users and gateway admins notices this and this needs fixing.   (was: When 
experiments are launched there are two records in EXPERIMENT SUMMARY table for 
LAUNCHED and EXECUTING state which has the exact same state change time. In PGA 
however two records show up for the same experiment and with same status. e.g.: 
two exact records for a dingle experiment. This only appears until the 
experiment is FAILED or COMPLETED. But both users and gateway admins notices 
this and this nee fixing. )

> Duplicating experiment records in Experiment statistics and Experiment browse
> -----------------------------------------------------------------------------
>
>                 Key: AIRAVATA-2376
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2376
>             Project: Airavata
>          Issue Type: Bug
>          Components: PGA PHP Web Gateway, Registry API
>    Affects Versions: 0.17
>         Environment: https://seagrid.org and all other gateways as well
>            Reporter: Eroma
>            Assignee: Marcus Christie
>             Fix For: 0.17
>
>
> When experiments are launched there are two records in EXPERIMENT SUMMARY 
> table for LAUNCHED and EXECUTING state which has the exact same state change 
> time. In PGA however two records show up for the same experiment and with 
> same status. e.g.: two exact records for a single experiment. This only 
> appears until the experiment is FAILED or COMPLETED. But both users and 
> gateway admins notices this and this needs fixing. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to