-
Bug
-
Resolution: Unresolved
-
Major
-
jBPM 4.3
The fork node starts the execution of both the branches in parallel by using inbuilt jBPM messaging. We have observed that the job executor picks up both the jobs and starts executing them concurrently. However the workflow never enters the join state.
- relates to
-
JBPM-2787 Process instances stuck in a fork
- Closed