Hi Xuan,

Are you running the tutorials or doing something different? Can you
explain. If you come across any issues while running the tutorials, please
report it under jira.

BTW you can report the issues here [1].

[1] - https://issues.apache.org/jira/browse/AIRAVATA

On Tue, Feb 28, 2012 at 5:34 PM, Xuan Wu <[email protected]> wrote:

> I fixed this by adding a new "Application Description", and use the same
> name "localecho" and executable/service("localecho")/host. It runs without
> exception now, but doesn't return for minutes, as "Stop workflow" is
> enabled. May I ask if it's normal even if the services are all local?
>
> Thanks,
>
> Xuan.
>
> On Tue, Feb 28, 2012 at 5:17 PM, Xuan Wu <[email protected]> wrote:
>
> > hi all,
> >
> > http://issues.apache.org/ seems to be down at the moment. So I may be
> > asking something that's solved already.
> >
> > Still I'm starting airavata locally. I'm trying to use the echo service I
> > created before, and I start XBaya, "Registry->Setup JCR Registry", and
> > "Application Services" show up in "Component" list, and there's
> "localecho"
> > under it.
> >
> > Then I open a workflow that's using the service I created before, and run
> > as before. It doesn't stop running, and airavata server gives this
> > exception:
> >
> > 305858 [Thread-18] INFO
> > org.apache.airavata.core.gfac.notification.impl.LoggingNotification -
> > -----DATA-----
> > 305858 [Thread-18] INFO
> > org.apache.airavata.core.gfac.notification.impl.LoggingNotification -
> Start
> > scheduling
> > 305858 [Thread-18] INFO
> > org.apache.airavata.core.gfac.notification.impl.LoggingNotification -
> > -----END DATA-----
> > 305868 [Thread-18] INFO
> > org.apache.airavata.core.gfac.scheduler.impl.SchedulerImpl - Searching
> > registry for some deployed application hosts
> > 305899 [Thread-18] WARN
> > org.apache.airavata.core.gfac.scheduler.impl.SchedulerImpl - Applcation
> > localecho not found in registry
> > 305900 [Thread-18] ERROR
> > org.apache.airavata.services.gfac.axis2.reciever.GFacMessageReciever -
> > Error in invoking service
> > org.apache.airavata.core.gfac.exception.SchedulerException: Host
> > Desciption for localecho does not found on resource Catalog
> > org.apache.airavata.registry.api.impl.AiravataJCRRegistry@b524aa
> > at
> >
> org.apache.airavata.core.gfac.scheduler.impl.SchedulerImpl.schedule(SchedulerImpl.java:83)
> > at
> >
> org.apache.airavata.core.gfac.services.impl.AbstractSimpleService.execute(AbstractSimpleService.java:88)
> > at
> >
> org.apache.airavata.services.gfac.axis2.reciever.GFacMessageReciever.invokeApplication(GFacMessageReciever.java:298)
> > at
> >
> org.apache.airavata.services.gfac.axis2.reciever.GFacMessageReciever.access$000(GFacMessageReciever.java:90)
> > at
> >
> org.apache.airavata.services.gfac.axis2.reciever.GFacMessageReciever$1.run(GFacMessageReciever.java:158)
> > 305900 [Thread-18] ERROR
> > org.apache.airavata.services.gfac.axis2.reciever.GFacMessageReciever -
> > Error invoking GFac Service
> > org.apache.airavata.core.gfac.exception.SchedulerException: Host
> > Desciption for localecho does not found on resource Catalog
> > org.apache.airavata.registry.api.impl.AiravataJCRRegistry@b524aa
> > at
> >
> org.apache.airavata.core.gfac.scheduler.impl.SchedulerImpl.schedule(SchedulerImpl.java:83)
> > at
> >
> org.apache.airavata.core.gfac.services.impl.AbstractSimpleService.execute(AbstractSimpleService.java:88)
> > at
> >
> org.apache.airavata.services.gfac.axis2.reciever.GFacMessageReciever.invokeApplication(GFacMessageReciever.java:298)
> > at
> >
> org.apache.airavata.services.gfac.axis2.reciever.GFacMessageReciever.access$000(GFacMessageReciever.java:90)
> > at
> >
> org.apache.airavata.services.gfac.axis2.reciever.GFacMessageReciever$1.run(GFacMessageReciever.java:158)
> >
> > In XBaya monitor, it shows:
> > 17:09:12.168 02/28/12 workflowInvoked einput=succes
> > 17:09:13.592 02/28/12 localecho_invoke invokingService einput=succes
> > 17:09:13.927 02/28/12 workflowInvoked [Workflow is invoked]
> >
> > Does this mean the service description is incomplete somehow? Or is this
> > the correct way to run an existing workflow?
> >
> > Thanks,
> >
> > Xuan.
> >
>



-- 
Regards,
Heshan Suriyaarachchi

http://heshans.blogspot.com/

Reply via email to