Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Critical
Fix Version/s: jBPM 3.2.9
Affects Version/s: jBPM 3.2.8
Component/s: Runtime Engine
Labels:
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

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

Assignee:: Alejandro Guizar (Inactive)

Reporter:: Alejandro Guizar (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 0 Start watching this issue

Created:: 2010/02/05 12:52 PM

Updated:: 2010/12/09 12:19 PM

Resolved:: 2010/03/11 5:07 AM