You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Eroma (JIRA)" <ji...@apache.org> on 2014/04/01 21:16:17 UTC
[jira] [Updated] (AIRAVATA-733) Lack of information on Xbaya
dashboard when wrong GSI credentials are setup at
airavata-server.properties
[ https://issues.apache.org/jira/browse/AIRAVATA-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eroma updated AIRAVATA-733:
---------------------------
Fix Version/s: 0.13
> Lack of information on Xbaya dashboard when wrong GSI credentials are setup at airavata-server.properties
> ---------------------------------------------------------------------------------------------------------
>
> Key: AIRAVATA-733
> URL: https://issues.apache.org/jira/browse/AIRAVATA-733
> Project: Airavata
> Issue Type: Bug
> Components: Airavata Client, Distribution, Security, XBaya
> Affects Versions: 0.6
> Environment: Mac OS 10.5.8
> Processor: 2 x 2.8GHz Quad-Core Intel Xeon
> Memory 8G 800 Mhz DDR2
> Java 1.6.0_26
> Path to Xbaya distribution I was using.
> trunk/modules/distribution/xbaya-gui/target/apache-airavata-xbaya-gui-0.6-SNAPSHOT/bin/
> I took the most recent code from repository this afternoon Jan/18/2013
> Reporter: Pedro da Silveira
> Priority: Minor
> Fix For: 0.13
>
>
> I prepared my workflow accordingly to my need to run at Lonestar.
> I clicked on the button "run my workflow", but button of the Xbaya dashboard in the section monitoring nothing changed.
> Follow a screenshot of my window.
> http://i48.tinypic.com/sf7xuc.jpg
> I checked the Airavata-server log to see what I didn't get any response.
> I had the error message below:
> [INFO] Experiment launched :WorkflowVLab_b17a7216-c13e-49e6-9ab0-07dff2431d88
> [INFO] -----DATA-----
> [INFO] Start scheduling
> [INFO] -----END DATA-----
> [INFO] Searching registry for some deployed application hosts
> [INFO] Found service on: lonestar4.tacc.teragrid.org
> [INFO] Found service on: lonestar4.tacc.teragrid.org
> [INFO] -----DATA-----
> [INFO] Finish scheduling
> [INFO] -----END DATA-----
> null
> Exception in thread "Thread-41" org.apache.airavata.workflow.model.exceptions.WorkflowRuntimeException: org.apache.airavata.workflow.tracking.WorkflowTrackingException: java.lang.RuntimeException: Publisher has been deleted!
> at org.apache.airavata.xbaya.interpretor.WorkflowInterpretorSkeleton.executeWorkflow(WorkflowInterpretorSkeleton.java:392)
> at org.apache.airavata.xbaya.interpretor.WorkflowInterpretorSkeleton.access$400(WorkflowInterpretorSkeleton.java:87)
> at org.apache.airavata.xbaya.interpretor.WorkflowInterpretorSkeleton$2.run(WorkflowInterpretorSkeleton.java:382)
> at java.lang.Thread.run(Thread.java:680)
> Caused by: org.apache.airavata.workflow.tracking.WorkflowTrackingException: java.lang.RuntimeException: Publisher has been deleted!
> at org.apache.airavata.workflow.tracking.AbstractNotifier.sendNotification(AbstractNotifier.java:160)
> at org.apache.airavata.workflow.tracking.impl.ProvenanceNotifierImpl.sendingFault(ProvenanceNotifierImpl.java:518)
> at org.apache.airavata.workflow.tracking.impl.ProvenanceNotifierImpl.sendingFault(ProvenanceNotifierImpl.java:485)
> at org.apache.airavata.xbaya.jython.lib.NotificationSender.workflowFailed(NotificationSender.java:262)
> at org.apache.airavata.xbaya.jython.lib.NotificationSender.workflowFailed(NotificationSender.java:226)
> at org.apache.airavata.xbaya.interpretor.WorkflowInterpreter.scheduleDynamically(WorkflowInterpreter.java:294)
> at org.apache.airavata.xbaya.interpretor.WorkflowInterpretorSkeleton.executeWorkflow(WorkflowInterpretorSkeleton.java:389)
> ... 3 more
> Caused by: java.lang.RuntimeException: Publisher has been deleted!
> at org.apache.airavata.workflow.tracking.impl.publish.WSMPublisher.publishSync(WSMPublisher.java:104)
> at org.apache.airavata.workflow.tracking.impl.publish.AbstractPublisher.publish(AbstractPublisher.java:95)
> at org.apache.airavata.workflow.tracking.AbstractNotifier.sendNotification(AbstractNotifier.java:158)
> ... 9 more
> I noticed that this message was happening because I didn't fill up the "airavata-server.properties" file correctly to use my GSI credentials.
--
This message was sent by Atlassian JIRA
(v6.2#6252)