airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Marru (JIRA)" <>
Subject [jira] [Resolved] (AIRAVATA-721) Xbaya attempt connection at a down Airavata Server
Date Wed, 26 Jun 2013 03:38:20 GMT


Suresh Marru resolved AIRAVATA-721.

    Resolution: Won't Fix
      Assignee: Suresh Marru

This error seems to be before XBaya was migrated to use REST API of registry. If this issue
still persists in latest (0.8) release testing, we need to re-open this and work on it for
> Xbaya attempt connection at a down Airavata Server
> --------------------------------------------------
>                 Key: AIRAVATA-721
>                 URL:
>             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
>            Assignee: Suresh Marru
>            Priority: Critical
>             Fix For: 0.8
> 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:

View raw message