This content has been marked as final.
Show 5 replies
-
1. Re: fork (concurrency) help
shettytejesh May 7, 2008 11:31 PM (in response to shettytejesh)heres snippet of xml which explains what i am doing....xml is schematically not correct but will give picture on what i am trying to achieve ..
-
2. Re: fork (concurrency) help
shettytejesh May 7, 2008 11:33 PM (in response to shettytejesh)<fork name='split'> <transition to='a' /> <transition to='b' /> <transition to='c' /> </fork> <node name='a'> <event type='node-enter'> <action class='ActionHAndler' /> </event> <transition to='joinit'> <action class='TransitionActionHandler' /> </transition> </node> <node name='b'> <event type='node-enter'> <action class='ActionHAndler' /> </event> <transition to='joinit'> <action class='TransitionActionHandler' /> </transition> </node> <node name='c'> <event type='node-enter'> <action class='ActionHAndler' /> </event> <transition to='joinit'> <action class='TransitionActionHandler' /> </transition> </node> <join name="joinit"> <event type='node-enter'> <action class='EnterJoinActionHandler' /> </event> <event type='node-leave'> <action class='LeaveJoinActionHandler' /> </event> <transition name="join-to-end" to='end' /> </join>
-
3. Re: fork (concurrency) help
kukeltje May 8, 2008 4:23 PM (in response to shettytejesh)jbpm does *not* make multiple threads for each of the legs of the forks.
-
4. Re: fork (concurrency) help
estaub May 8, 2008 4:29 PM (in response to shettytejesh)Adding async="true" to the node on each leg will make it execute independently. I don't know how/if this works if you are not persisting; someone else may know. If you are persisting, you'll need to use a database with good isolation and transaction characteristics - in particular, not HSQL.
-
5. Re: fork (concurrency) help
shettytejesh May 8, 2008 4:35 PM (in response to shettytejesh)After posting my question and going through the jbpm doc, I did understood the GOP execution strategy and realized I will have to use async='true'.
Thanks for the help.