[
https://jira.jboss.org/jira/browse/JBPM-1991?page=com.atlassian.jira.plug...
]
Alejandro Guizar commented on JBPM-1991:
----------------------------------------
Q: What use do you make of the lock attribute?
A: You can set the lock attribute to 'READ' to avoid the pessimistic lock if your
process does not have contention at the join node, or 'FORCE' to acquire both
locks (pessimistic and optimistic) if you wanted to be really sure no contention will take
place.
Change default parentLockMode from FORCE to UPGRADE
---------------------------------------------------
Key: JBPM-1991
URL:
https://jira.jboss.org/jira/browse/JBPM-1991
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Core Engine
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM-3.2.5.SP1, jBPM 3.2.6 GA
According to the Hibernate documentation, LockMode.FORCE is "similar to UPGRADE
except that, for versioned entities, it results in a forced version increment". The
version increment often produces undue stale state exceptions under databases that support
isolation levels above READ_UNCOMMITTED, i.e. all except HSQLDB.
Under HSQLDB, LockMode.FORCE provides a simplistic work-around the lack of isolation.
Unfortunately it does not constitute a real solution since dirty reads can occur anywhere
else, causing all kinds of "weird" assertion failures. Every test case that
exercises concurrency has been excluded from the HSQLDB test suite due to its
unreliability.
Therefore, no reason remains to keep the default parentLockMode at FORCE.
--
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