Flow activity might not reactivate parent token in race condition
-----------------------------------------------------------------
Key: BPEL-260
URL:
http://jira.jboss.com/jira/browse/BPEL-260
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Priority: Critical
Fix For: jBPM BPEL 1.1 GA
The flow activity suffers from the same problem as the join node in jPDL. When child
tokens complete the nested activities concurrently, it is possible that all of them
determine that the parent token must not be reactivated yet, leading to deadlock. The
cause of this behavior is transaction isolation.
To prevent this problem, the code to leave the flow must acquire exclusive access to the
state of the concurrent tokens.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: