-
Bug
-
Resolution: Done
-
Major
-
jBPM 6.4.0.Final
-
None
-
NEW
-
NEW
-
Workaround Exists
-
-
When more than one deployment unit is deployed, the processes definition in the second deployment is not found.
The issue is that the same ksession is used when deploying and creating a RuntimeManager from different deployment units. The RuntimeManager is different though.
It happens for Per Request strategy, but works well for Per Process Instance.
- clones
-
RHBPMS-4153 [GSS](6.3.z) "Process Not Found" when deploying more than one DeploymentUnit in BPM Suite 6.3 using PER REQUEST strategy
- Verified