You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by Hasitha Aravinda <ma...@gmail.com> on 2012/06/29 06:48:26 UTC

Problem in Executing Intermediate Nodes in Workflow Interpreter using current trunk

Hi Devs,

Currently I am working on implementing debugging functionalities for
intermediate Nodes. Now I am Having some problems in testing those
functionalities.

This is the problem,

In scheduleDynamically() method in WorklfowInterpretor, After it reads
inputs nodes, It comes to a line which checks current "readyNodes".
(ArrayList<Node> readyNodes = this.getReadyNodesDynamically(); )

The problems is this readyNodes count always becomes 0. This causes to
run Interpretor in an infinite loop and never allows to execute
intermediate nodes( IF, ForEach, WSNode, etc.) using
executeDynamically(node) method. I tested interpreter using
SimpleMathWorkflowTest and got the same result. Then I build xbaya-gui
using maven (including tests ) and got the same result.

Then I tried it using a fresh copy of the trunk (R1355237), to verify
that this is not because of the local modification which i done to the
WorklfowInterpretor. And it seems problem present in trunk as well .

This is a blocker to continue implementation of the debugger module.
Can you please have a look about this problem.

Thanks,
Hasitha

Re: Problem in Executing Intermediate Nodes in Workflow Interpreter using current trunk

Posted by Hasitha Aravinda <ma...@gmail.com>.
Hi Lahiru,

Now it works fine.

Thanks,
Hasitha.

On Fri, Jun 29, 2012 at 7:35 PM, Lahiru Gunathilake <gl...@gmail.com> wrote:
> On Fri, Jun 29, 2012 at 12:48 AM, Hasitha Aravinda <mail.hasitha27@gmail.com
>> wrote:
>
>> Hi Devs,
>>
>> Currently I am working on implementing debugging functionalities for
>> intermediate Nodes. Now I am Having some problems in testing those
>> functionalities.
>>
>> This is the problem,
>>
>> In scheduleDynamically() method in WorklfowInterpretor, After it reads
>> inputs nodes, It comes to a line which checks current "readyNodes".
>> (ArrayList<Node> readyNodes = this.getReadyNodesDynamically(); )
>>
>> The problems is this readyNodes count always becomes 0. This causes to
>> run Interpretor in an infinite loop and never allows to execute
>> intermediate nodes( IF, ForEach, WSNode, etc.) using
>> executeDynamically(node) method. I tested interpreter using
>> SimpleMathWorkflowTest and got the same result. Then I build xbaya-gui
>> using maven (including tests ) and got the same result.
>>
>> Then I tried it using a fresh copy of the trunk (R1355237), to verify
>> that this is not because of the local modification which i done to the
>> WorklfowInterpretor. And it seems problem present in trunk as well .
>>
>> This is a blocker to continue implementation of the debugger module.
>> Can you please have a look about this problem.
>>
> Hasitha,
>
> I just fixed this issue !
>
> Can you take an svn update and see whether it solves your issue.
>
> Lahiru
>
>>
>> Thanks,
>> Hasitha
>>
>
>
>
> --
> System Analyst Programmer
> PTI Lab
> Indiana University

Re: Problem in Executing Intermediate Nodes in Workflow Interpreter using current trunk

Posted by Lahiru Gunathilake <gl...@gmail.com>.
On Fri, Jun 29, 2012 at 12:48 AM, Hasitha Aravinda <mail.hasitha27@gmail.com
> wrote:

> Hi Devs,
>
> Currently I am working on implementing debugging functionalities for
> intermediate Nodes. Now I am Having some problems in testing those
> functionalities.
>
> This is the problem,
>
> In scheduleDynamically() method in WorklfowInterpretor, After it reads
> inputs nodes, It comes to a line which checks current "readyNodes".
> (ArrayList<Node> readyNodes = this.getReadyNodesDynamically(); )
>
> The problems is this readyNodes count always becomes 0. This causes to
> run Interpretor in an infinite loop and never allows to execute
> intermediate nodes( IF, ForEach, WSNode, etc.) using
> executeDynamically(node) method. I tested interpreter using
> SimpleMathWorkflowTest and got the same result. Then I build xbaya-gui
> using maven (including tests ) and got the same result.
>
> Then I tried it using a fresh copy of the trunk (R1355237), to verify
> that this is not because of the local modification which i done to the
> WorklfowInterpretor. And it seems problem present in trunk as well .
>
> This is a blocker to continue implementation of the debugger module.
> Can you please have a look about this problem.
>
Hasitha,

I just fixed this issue !

Can you take an svn update and see whether it solves your issue.

Lahiru

>
> Thanks,
> Hasitha
>



-- 
System Analyst Programmer
PTI Lab
Indiana University