As I know, ODE takes an instance lock for executing actions inside a process. So this looks like something not to overcome easily.
2009/3/24 <[email protected]>: > Hi all, > > the problem seems not to be related to extension activities only. I did a > test invoking webservices: > > ... > <flow> > <invoke name="sayHi" partnerLink="HelloWorld" > portType="hw:HelloWorld" operation="sayHi" inputVariable="hi" > outputVariable="response"> > </invoke> > > <invoke name="sayHo" partnerLink="HelloWorld" > portType="hw:HelloWorld" operation="sayHi" inputVariable="ho" > outputVariable="response2"> > </invoke> > </flow> > ... > > The two invoke elements are executed in random order. However the second > invoke call is not executed until the first invoke returns. It seems that the > same Thread is used to execute the invoke calls. We use the integrated > SimpleScheduler. > > Anyone any ideas what's going wrong here ? > > Bye, > Daniel > > >> -----Ursprüngliche Nachricht----- >> Von: [email protected] [mailto:[email protected]] >> Gesendet: Montag, 23. März 2009 18:32 >> An: [email protected] >> Betreff: Problem with flow and extension activities >> >> Hi all, >> >> in the SMILA project we are using extension activities to execute > java >> code in BPEL. This works without any problems. >> >> Now I tried to execute two extension activities concurrently within a >> <flow> (see attachment). The execution still works, but the extension >> activities are not executed concurrently but in sequence. I debugged >> and >> found that the extension activities are executed by the same thread. >> >> We currently use ODE 2.0. >> >> Is there any error on my bpel workflow ? Or is there a ThreadPool >> that's >> size needs to be increased ? Or some other configuration option ? >> >> Thanks for your help! >> >> Bye, >> Daniel > > -- Rafał Rusin http://www.touk.pl http://www.mimuw.edu.pl/~rrusin
