[jboss-user] [jBPM] - Joining of non-concurrent decision paths seems to be broken in 4.4

Maciej Swiderski do-not-reply at jboss.com
Mon Aug 9 15:28:00 EDT 2010

Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] replied to the discussion

"Joining of non-concurrent decision paths seems to be broken in 4.4"

To view the discussion, visit: http://community.jboss.org/message/556548#556548

Hi guys,

the issue is not related to nested forks, in fact it is caused by too many joins compared to fork. As you can see first join that is used to merge executions that where split by decision activity is not aware that there will be any other join later on. When execution arrives to it, join is completed based on the multiplicity attribute and ends any other not joined paths.

You could change your process definition to remove join1 and point all to join2 and set multiplicity attribute on it to 2, that would probably work just fine. 

I agree that a good practice would be to use gateways to join exclusive paths but it looks to me (correct me if I am wrong) that somehow we are mixing two types of gateways here - exclusive at the beginning and then parallel.

This feature was introduced to make sure we are not going to leave any orphans when join is completed.

Let me know what do you think about it.



Reply to this message by going to Community

Start a new discussion in jBPM at Community

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20100809/ef32956c/attachment-0001.html 

More information about the jboss-user mailing list