[jbpm-issues] [JBoss JIRA] Updated: (JBPM-2787) Process instances stuck in a fork
[
https://jira.jboss.org/jira/browse/JBPM-2787?page=com.atlassian.jira.plug...
]
Alejandro Guizar updated JBPM-2787:
-----------------------------------
To prevent concurrent tokens from getting stuck in a join node, each concurrent token ends
when it enters the join node. Ending a token normally makes it unable to reactivate its
parent token, but this ability is restored. Afterwards, the join execute method confirms
all children of the parent token have ended before checking for the parent token
reactivation flag.
Combined with making the join node asynchronous, ending each concurrent token on entry
makes less likely that a sibling token misses its arrival and gets stuck in the join.
Process instances stuck in a fork
---------------------------------
Key: JBPM-2787
URL: https://jira.jboss.org/jira/browse/JBPM-2787
Project: jBPM
Issue Type: Bug
Components: Runtime Engine
Affects Versions: jBPM 3.2.8
Environment: 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
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Priority: Critical
Fix For: jBPM 3.2.9
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira