[jira] [Updated] (AIRAVATA-2376) Duplicating experiment records in Experiment statistics and Experiment browse

2017-06-13 Thread Marcus Christie (JIRA)

 [ 
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. 

h3. Resources

* MySQL JDBC driver configuration:
** 
https://dev.mysql.com/doc/connector-j/5.1/en/connector-j-reference-configuration-properties.html
** uses sendFractionalSeconds
** added in [MySQL Connector/J 
5.1.37|https://docs.oracle.com/cd/E17952_01/connector-j-relnotes-en/news-5-1-37.html]
* https://issues.apache.org/jira/browse/OPENJPA-2159
* MariaDB JDBC driver configuration:
** https://mariadb.com/kb/en/mariadb/about-mariadb-connector-j/
** uses useFractionalSeconds
* MariaDB JDBC driver defaults to useFractionalSeconds as true since 1.1.8
** https://mariadb.com/kb/en/mariadb/mariadb-java-client-118-changelog/
* [MariaDB TIMESTAMP|https://mariadb.com/kb/en/mariadb/timestamp/]
* [Microseconds in 
MariaDB|https://mariadb.com/kb/en/mariadb/microseconds-in-mariadb/]
* How to specify TIMESTAMP precision in JPA annotations?
** [Confused why they seem to use scale instead of precision in 
OpenJPA|https://issues.apache.org/jira/browse/OPENJPA-2555]
* [Supporting evidence that we need to use MariaDB driver when using MariaDB 
server|https://issues.alfresco.com/jira/browse/MNT-17613]




  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 single experiment. This only appears until the 
experiment is FAILED or COMPLETED. But both users and gateway admins notices 
this and this needs fixing. 

h3. Resources

* MySQL JDBC driver configuration:
** 
https://dev.mysql.com/doc/connector-j/5.1/en/connector-j-reference-configuration-properties.html
** uses sendFractionalSeconds
** added in [MySQL Connector/J 
5.1.37|https://docs.oracle.com/cd/E17952_01/connector-j-relnotes-en/news-5-1-37.html]
* https://issues.apache.org/jira/browse/OPENJPA-2159
* MariaDB JDBC driver configuration:
** https://mariadb.com/kb/en/mariadb/about-mariadb-connector-j/
** uses useFractionalSeconds
* MariaDB JDBC driver defaults to useFractionalSeconds as true since 1.1.8
** https://mariadb.com/kb/en/mariadb/mariadb-java-client-118-changelog/
* [MariaDB TIMESTAMP|https://mariadb.com/kb/en/mariadb/timestamp/]
* [Microseconds in 
MariaDB|https://mariadb.com/kb/en/mariadb/microseconds-in-mariadb/]
* How to specify TIMESTAMP precision in JPA annotations?
** [Confused why they seem to use scale instead of precision in 
OpenJPA|https://issues.apache.org/jira/browse/OPENJPA-2555]





> 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
>Priority: Critical
> 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. 
> h3. Resources
> * MySQL JDBC driver configuration:
> ** 
> https://dev.mysql.com/doc/connector-j/5.1/en/connector-j-reference-configuration-properties.html
> ** uses sendFractionalSeconds
> ** added in [MySQL Connector/J 
> 5.1.37|https://docs.oracle.com/cd/E17952_01/connector-j-relnotes-en/news-5-1-37.html]
> * https://issues.apache.org/jira/browse/OPENJPA-2159
> * MariaDB JDBC driver configuration:
> ** https://mariadb.com/kb/en/mariadb/about-mariadb-connector-j/
> ** uses useFractionalSeconds
> * MariaDB JDBC driver defaults to useFractionalSeconds as true since 1.1.8
> ** https://mariadb.com/kb/en/mariadb/mariadb-java-client-118-changelog/
> * [MariaDB TIMESTAMP|https://mariadb.com/kb/en/mariadb/timestamp/]
> * [Microseconds in 
> 

[jira] [Updated] (AIRAVATA-2376) Duplicating experiment records in Experiment statistics and Experiment browse

2017-06-13 Thread Marcus Christie (JIRA)

 [ 
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. 

h3. Resources

* MySQL JDBC driver configuration:
** 
https://dev.mysql.com/doc/connector-j/5.1/en/connector-j-reference-configuration-properties.html
** uses sendFractionalSeconds
** added in [MySQL Connector/J 
5.1.37|https://docs.oracle.com/cd/E17952_01/connector-j-relnotes-en/news-5-1-37.html]
* https://issues.apache.org/jira/browse/OPENJPA-2159
* MariaDB JDBC driver configuration:
** https://mariadb.com/kb/en/mariadb/about-mariadb-connector-j/
** uses useFractionalSeconds
* MariaDB JDBC driver defaults to useFractionalSeconds as true since 1.1.8
** https://mariadb.com/kb/en/mariadb/mariadb-java-client-118-changelog/
* [MariaDB TIMESTAMP|https://mariadb.com/kb/en/mariadb/timestamp/]
* [Microseconds in 
MariaDB|https://mariadb.com/kb/en/mariadb/microseconds-in-mariadb/]
* How to specify TIMESTAMP precision in JPA annotations?
** [Confused why they seem to use scale instead of precision in 
OpenJPA|https://issues.apache.org/jira/browse/OPENJPA-2555]




  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 single experiment. This only appears 
until the experiment is FAILED or COMPLETED. But both users and gateway admins 
notices this and this needs 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
>Priority: Critical
> 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. 
> h3. Resources
> * MySQL JDBC driver configuration:
> ** 
> https://dev.mysql.com/doc/connector-j/5.1/en/connector-j-reference-configuration-properties.html
> ** uses sendFractionalSeconds
> ** added in [MySQL Connector/J 
> 5.1.37|https://docs.oracle.com/cd/E17952_01/connector-j-relnotes-en/news-5-1-37.html]
> * https://issues.apache.org/jira/browse/OPENJPA-2159
> * MariaDB JDBC driver configuration:
> ** https://mariadb.com/kb/en/mariadb/about-mariadb-connector-j/
> ** uses useFractionalSeconds
> * MariaDB JDBC driver defaults to useFractionalSeconds as true since 1.1.8
> ** https://mariadb.com/kb/en/mariadb/mariadb-java-client-118-changelog/
> * [MariaDB TIMESTAMP|https://mariadb.com/kb/en/mariadb/timestamp/]
> * [Microseconds in 
> MariaDB|https://mariadb.com/kb/en/mariadb/microseconds-in-mariadb/]
> * How to specify TIMESTAMP precision in JPA annotations?
> ** [Confused why they seem to use scale instead of precision in 
> OpenJPA|https://issues.apache.org/jira/browse/OPENJPA-2555]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (AIRAVATA-2376) Duplicating experiment records in Experiment statistics and Experiment browse

2017-06-09 Thread Marcus Christie (JIRA)

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

Marcus Christie updated AIRAVATA-2376:
--
Priority: Critical  (was: Major)

> 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
>Priority: Critical
> 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)


[jira] [Updated] (AIRAVATA-2376) Duplicating experiment records in Experiment statistics and Experiment browse

2017-05-01 Thread Marcus Christie (JIRA)

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