Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1F154119F0 for ; Fri, 10 May 2013 02:53:16 +0000 (UTC) Received: (qmail 56328 invoked by uid 500); 10 May 2013 02:53:16 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 56296 invoked by uid 500); 10 May 2013 02:53:15 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 56286 invoked by uid 99); 10 May 2013 02:53:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 May 2013 02:53:15 +0000 Date: Fri, 10 May 2013 02:53:15 +0000 (UTC) From: "Chathuri Wimalasena (JIRA)" To: dev@airavata.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AIRAVATA-849) Error messages from Airavata API MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AIRAVATA-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653497#comment-13653497 ] Chathuri Wimalasena commented on AIRAVATA-849: ---------------------------------------------- Hi Raman, Did you try increasing wait_timeout in MySQL. I could not find any property that we can set from JPA side. People recommend to increase wait_timeout global parameter from default 28800 to a bigger number. Chathuri > Error messages from Airavata API > -------------------------------- > > Key: AIRAVATA-849 > URL: https://issues.apache.org/jira/browse/AIRAVATA-849 > Project: Airavata > Issue Type: Bug > Components: Airavata Client > Affects Versions: 0.8 > Reporter: Raminderjeet Singh > > Main error messages thrown from Airavata API are not useful. We always give this error org.apache.airavata.client.api.AiravataAPIInvocationException: Error invoking API if someone is doing a getLocalMessage in the error trace. Main error is hidden way down in the error stack. If you see the following error log, we have the right error coming from log message but when i tried to do e.getLocalizedMessage() to return the calling service i just get "java.lang.RuntimeException: org.apache.airavata.client.api.AiravataAPIInvocationException: Error invoking API". We need improve throwing the right error message to the client. > [INFO] Calling airavata client to run US3-test-stampede > [INFO] Submitting the request with airavata on http://156.56.104.85:7070/airavata-server/services/WorkflowInterpretor > [ERROR] The workflow US3_Service does not exists in user space!!! > org.apache.airavata.registry.api.exception.worker.UserWorkflowDoesNotExistsException: The workflow US3_Service does not exists in user space!!! > at org.apache.airavata.persistance.registry.jpa.impl.AiravataJPARegistry.getWorkflowGraphXML(AiravataJPARegistry.java:1109) > at org.apache.airavata.client.impl.WorkflowManagerImpl.getWorkflowAsString(WorkflowManagerImpl.java:221) > at org.apache.airavata.client.impl.WorkflowManagerImpl.getWorkflow(WorkflowManagerImpl.java:214) > at org.apache.airavata.client.impl.WorkflowManagerImpl.getWorkflow(WorkflowManagerImpl.java:335) > at org.apache.airavata.client.impl.WorkflowManagerImpl.getWorkflowInputs(WorkflowManagerImpl.java:464) > at org.ogce.airavata.client.UltrascanRun.runWorkflow(UltrascanRun.java:150) > at org.ogce.airavata.client.UltrascanRun.runWorkflow(UltrascanRun.java:132) > at org.ogce.gram.job.AiravataJobRun$JobRunner.call(AiravataJobRun.java:374) > at org.ogce.gram.job.AiravataJobRun$JobRunner.call(AiravataJobRun.java:363) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > [ERROR] Error invoking API > org.apache.airavata.client.api.AiravataAPIInvocationException: Error invoking API > at org.apache.airavata.client.impl.WorkflowManagerImpl.getWorkflowAsString(WorkflowManagerImpl.java:223) > at org.apache.airavata.client.impl.WorkflowManagerImpl.getWorkflow(WorkflowManagerImpl.java:214) > at org.apache.airavata.client.impl.WorkflowManagerImpl.getWorkflow(WorkflowManagerImpl.java:335) > at org.apache.airavata.client.impl.WorkflowManagerImpl.getWorkflowInputs(WorkflowManagerImpl.java:464) > at org.ogce.airavata.client.UltrascanRun.runWorkflow(UltrascanRun.java:150) > at org.ogce.airavata.client.UltrascanRun.runWorkflow(UltrascanRun.java:132) > at org.ogce.gram.job.AiravataJobRun$JobRunner.call(AiravataJobRun.java:374) > at org.ogce.gram.job.AiravataJobRun$JobRunner.call(AiravataJobRun.java:363) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Caused by: org.apache.airavata.registry.api.exception.worker.UserWorkflowDoesNotExistsException: The workflow US3_Service does not exists in user space!!! > at org.apache.airavata.persistance.registry.jpa.impl.AiravataJPARegistry.getWorkflowGraphXML(AiravataJPARegistry.java:1109) > at org.apache.airavata.client.impl.WorkflowManagerImpl.getWorkflowAsString(WorkflowManagerImpl.java:221) > ... 12 more > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira