please post again, things got lost...
This is a piece of my process definition :
<decision g="132,161,80,40" name="ChooseWorker" continuation="async">
<handler class="be.myorganisation.myapp.WorkerDecisionHandler" />
<transition g="-6,-18" name="groupOne" to="inTreatmentByGroupOne"/>
<transition g="-42,-17" name="groupTwo" to="inTreatmentByGroupTwo"/>
Thanks for helping,
A lot more info was missing. It is btw always better to post it as a unittest. That way we can try to reproduce easily.
I'm going to try now, but you should to and at least use jbpm 4.3 (not 4.0 as your pom states!!!!)
Ok, your test runs and is green here, but only one line ouput. There is no decisionhandler called as I would expect since you have no jobscheduler configured in your config. In that case you should run it 'manually' in the testcase. See the jBPM source (modules/test-db/.... ) for examples.
And if I enable the jobscheduler in the config, it still is green, with two lines of output AND different thread names.
So advice: update to jbpm 4.3 and usea job scheduler if you want two threads
The update to 4.3 I already did yesterday. Changing the config like you mentioned did the trick.
Thanks for your great help!