Issue

We have a parent and a sub-process. When we signal the last wait state in the sub-process, we have noticed a different behaviour between jbpm 3.2.8 and 3.2.10. In jBPM 3.2.8, the signaling of the parent process happened in the same transaction, whereas in jBPM 3.2.10 a signaling job is created, which will then be executed by the messaging component asynchronously in a new transaction.

As we don't use any async attribute, we don't want this asyncronous behavior.

Can the sub-process signaling behavior be reverted to be synchronous again?