-
Bug
-
Resolution: Done
-
Critical
-
jBPM 3.2.8
-
None
-
SOA 4.3 CP02 with jBPM 3.2.8_SOA
2 node cluster
Oracle DB with xa datasources
JMS-based messaging/scheduler services from the SOA-P
There are problems with a jBPM process which contains a fork/join when running in a cluster.
If run with just one node, the processes end properly, but with two nodes the child tokens don't reactivate the parent token
Any ideas? Such as:
- specifying <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation> on the JbpmDS
- trying lock="UPGRADE_NOWAIT" on the join
- incorporates
-
JBPM-2139 Concurrency problems with the Join node despite lock="pessimistic"
-
- Resolved
-
- is incorporated by
-
JBPM-2790 StaleObjectStateException: "Row was updated or deleted by another transaction" frequently thrown when joining forked tokens
-
- Resolved
-
- is related to
-
JBPM-2888 executions stuck in join activity
-
- Open
-