On Wed, Nov 19, 2008 at 12:48 AM, Vineesh Thomas <[EMAIL PROTECTED]> wrote:

>
> Hi,
>
> I am facing some trouble with parallel processing in my BPEL(running ODE on
> Tomcat 5.5.x).
>
> I have a flow(flow1) with three sequences (seq1,seq2 & seq3) in it.
>
> My BPEL begins with a receive tag followed by this <flow> tag which has
> these 3 <sequences>. In each of these 3 tags I am invoking some other
> webservice and then waiting for a callback.
>
> Coming to my problem: Once the BPEL execution starts after receiving the
> input request the control goes to the flow. But all three sequences do not
> start up simultaneously. Most of the times only 2 out of the 3 sequences
> starts up and the external webservice is invoked for them. Only after I
> restart the tomcat(without deploying the process) the third sequence gets
> activated and its corresponding invoke happens.
>
> Once I didn't restart the tomcat for very long time (around 30-45 minutes)
> and then the third sequence got activated and then the rest of the process
> continued.
>
> Could someone please explain this behavior. :confused:
>

It's indeed a strange behavior and I've never witnessed any similar problem.
We do have a few test cases with similar layouts (see [1] and [2]). Did you
try to enable more logs to get a better idea of what happens? Can you tell
me more about your environment (version of ODE, war or jbi, ...)?


>
> Also I'd like to know if there is any upper limit on the number of
> sequences
> one can have in a flow in ODE?
>

Definitely not, you can have as many sequences as you want.

Matthieu

[1]
http://svn.apache.org/repos/asf/ode/trunk/bpel-test/src/test/resources/bpel/2.0/TestFlowActivity1/TestActivityFlow.bpel
[2]
http://svn.apache.org/repos/asf/ode/trunk/bpel-test/src/test/resources/bpel/2.0/TestFlowLinks/TestCase.bpel


>
> Thanks,
> Vineesh.:working:
> --
> View this message in context:
> http://www.nabble.com/Trouble-with-flows...-tp20575751p20575751.html
> Sent from the Apache Ode Dev mailing list archive at Nabble.com.
>
>

Reply via email to