[
https://issues.apache.org/jira/browse/AIRAVATA-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eroma closed AIRAVATA-1375.
---------------------------
Resolution: Fixed
Tried to recreate the reported error in
http://dev.test-drive.airavata.org/portal/pga/public and in
http://test-drive.airavata.org/pga/public. Couldn't recreate it; seems like it
is been fixed
Tested and verified
> In PHP gateway after login in; Create Experiment screen gives the attached
> Error on Compute Resources
> -----------------------------------------------------------------------------------------------------
>
> Key: AIRAVATA-1375
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1375
> Project: Airavata
> Issue Type: Bug
> Affects Versions: 0.13
> Reporter: Eroma
>
> In PHP gateway after login in; Create Experiment screen gives the attached
> Error on Compute Resources.
> In the PHP gateway after login in; Entered a Experiment name and clicked on
> 'Continue' button.
> Gave the below chunky error message
> There was a problem getting compute resources. Please try again later or
> submit a bug report using the link in the Help menu.
> Airavata System Exception: Error while saving compute resource. More info
> :org.apache.openjpa.persistence.PersistenceException: The last packet
> successfully received from the server was 160,728,925 milliseconds ago. The
> last packet sent successfully to the server was 160,728,926 milliseconds ago.
> is longer than the server configured value of 'wait_timeout'. You should
> consider either expiring and/or testing connection validity before use in
> your application, increasing the server configured values for client
> timeouts, or using the Connector/J connection property 'autoReconnect=true'
> to avoid this problem. FailedObject: SELECT p FROM ApplicationInterface p
> WHERE p.interfaceID =:param0 [java.lang.String]
> Observation;
> Not only in the Create experiment screen but if the user search for
> experiments or projects which has experiment This error message is given only
> if it is the action taken just after login in to the gateway (not all the
> time but seems like after a new release or a server start up). After the
> first attempt this message vanishes; do nest appear again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
