[
https://issues.apache.org/jira/browse/AIRAVATA-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561213#comment-13561213
]
Pedro da Silveira commented on AIRAVATA-721:
--------------------------------------------
Hi Chathuri,
You are right. At least on the revision 1437790 the Component list is not
repeated. Although, it still lacks an warn message on screen to alert the user
the Airavata-Server is down or not responding.
> Xbaya attempt connection at a down Airavata Server
> --------------------------------------------------
>
> Key: AIRAVATA-721
> URL: https://issues.apache.org/jira/browse/AIRAVATA-721
> Project: Airavata
> Issue Type: Bug
> Components: 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/
> Reporter: Pedro da Silveira
> Priority: Critical
> Fix For: 0.7
>
>
> I was working on my workflow on Airavata, I had some problems after
> submitting at Ranger.
> I had to restart the Xbaya and Airavata-server in order to continue.
> I only restart the Xbaya and forgot to start the Airavata Server.
> On Xbaya I went to Xbaya => import => Workflow from Registry. I just left the
> standard Airavata Registry setting and hit the ok button.
> No error message appeared on my Xbaya screen. I didn't know what to do. I
> repeated the process above to import my workflow from Registry.
> I just noticed that at every attempt a new Application Service was added on
> the left menu Component List.
> That's when I realized my Airavata-server was down.
--
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
