airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pedro da Silveira (JIRA)" <>
Subject [jira] [Created] (AIRAVATA-732) Unexpected error when Import workflow from Registry
Date Fri, 18 Jan 2013 21:50:13 GMT
Pedro da Silveira created AIRAVATA-732:

             Summary: Unexpected error when Import workflow from Registry
                 Key: AIRAVATA-732
             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.

I took the most recent code this afternoon Jan/18/2013
            Reporter: Pedro da Silveira

I started a fresh copy of Xbaya and Airavata-Server I download this afternoon Jan/18/2013.
I went straight to setup my Application Services. After I got done. I went to menu Xbaya =>
Import => Workflow from Registry. I got the error message: "Unexpected Error" and the line
of code showed below:

org.apache.airavata.client.api.AiravataAPIInvocationException: Error invoking API
	at org.apache.airavata.client.impl.WorkflowManagerImpl.getWorkflows(
	at org.apache.airavata.client.impl.WorkflowManagerImpl.getWorkflows(
	at org.apache.airavata.xbaya.registry.RegistryAccesser.getOGCEWorkflowTemplateList(
	at org.apache.airavata.xbaya.ui.experiment.RegistryLoaderWindow$
Caused by: com.sun.jersey.api.client.UniformInterfaceException: GET http://localhost:8080/airavata-registry/api/userwfregistry/get/workflows
returned a response status of 204 No Content
	at com.sun.jersey.api.client.ClientResponse.getEntity(
	at com.sun.jersey.api.client.ClientResponse.getEntity(
	at org.apache.airavata.client.impl.WorkflowManagerImpl.getWorkflows(
	... 3 

I know that I shouldn't import any workflow from Registry since it was a fresh installation
of Airavata. 

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