-
Bug
-
Resolution: Done
-
Major
-
jBPM 3.2.2
-
None
-
None
If in one transaction you create a new process instance and reach a join, you'll get a invalid StaleObjectStateException. The cause is that in case of oracle, hibernate will not insert the record in the database before the forced version increment in the join will be executed. That results in 0 rows updated and hence a StaleStateObjectException.
The fix applied is that we added a flush before the forced version update in the join
- is duplicated by
-
JBPM-1886 Oracle causing StaleObjectStateException
- Closed