2 Replies Latest reply on Apr 29, 2009 5:11 AM by John Sweet-Escott

    Strategies on concurrent execution of FORK-JOIN execution pa

    Chetan Kadam Newbie

      Hi All,

      I am using jbpm version 3.2.6.sp1. (recently upgraded from 3.1.4). One of the business scenarios I am trying to support is, to be able to run multiple branches in FORK-JOIN execution paths concurrently. I have searched this user forum as well as wiki for possible ways of implementing this scenario.

      Here is my understanding, and I was hoping to validate it from some of you, who may have implemented something similar:

      1. Use of ASYNC=true on node, which will queue execution of Node-Actions using JMS. Default fork handler will create child tokens for each possible transition in the fork definition and will be able to signal them right away (since each child token signal call would return right away after queuing the action).

      2. I could write custom fork handler Or some client process executor, which creates child token for each transition and submits token.signal() calls in separate threads. (i.e. client would manage the threads for each execution paths). However, I am afraid, I might run into some hibernate concurrency issues (when updating process instance).

      Does anyone have better suggestions ? or experience with such implementations. Any pointers / suggestions are very much appreciated.

      Thanks !