airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raminderjeet Singh (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (AIRAVATA-824) EmbeddedGFacInvoker is not reading hostname from application scheduling context
Date Fri, 19 Apr 2013 15:25:15 GMT

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

Raminderjeet Singh reopened AIRAVATA-824:
-----------------------------------------


[INFO] Experiment launched :Workflow1_93c69f83-1875-413d-84c7-a14a3ff0bf52
[ERROR]
java.lang.IndexOutOfBoundsException
at
org.apache.airavata.schemas.wec.impl.WorkflowSchedulingContextDocumentImpl$WorkflowSchedulingContextImpl.getApplicationSchedulingContextArray(Unknown
Source)
at
org.apache.airavata.xbaya.invoker.EmbeddedGFacInvoker.invoke(EmbeddedGFacInvoker.java:286)
at
org.apache.airavata.xbaya.interpretor.WorkflowInterpreter.handleWSComponent(WorkflowInterpreter.java:685)
at
org.apache.airavata.xbaya.interpretor.WorkflowInterpreter.executeDynamically(WorkflowInterpreter.java:504)
at
org.apache.airavata.xbaya.interpretor.WorkflowInterpreter.scheduleDynamically(WorkflowInterpreter.java:189)
at
org.apache.airavata.xbaya.interpretor.WorkflowInterpretorSkeleton.executeWorkflow(WorkflowInterpretorSkeleton.java:385)
at
org.apache.airavata.xbaya.interpretor.WorkflowInterpretorSkeleton.access$400(WorkflowInterpretorSkeleton.java:78)
at org.apache.airavata.xbaya.interpretor.Wo
                
> EmbeddedGFacInvoker is not reading hostname from application scheduling context
> -------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-824
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-824
>             Project: Airavata
>          Issue Type: Bug
>    Affects Versions: 0.8
>            Reporter: Raminderjeet Singh
>            Assignee: Raminderjeet Singh
>             Fix For: 0.8
>
>


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

Mime
View raw message