[jbpm-issues] [JBoss JIRA] Commented: (JBPM-1953) Select the Lock Strategy in jbpm.cfg.xml
[
https://jira.jboss.org/jira/browse/JBPM-1953?page=com.atlassian.jira.plug...
]
Alejandro Guizar commented on JBPM-1953:
----------------------------------------
The lock strategy cannot be simply specified in jbpm.cfg.xml. Hibernate offers no way to
disable version checking. Entities that declare a version column in their corresponding
mapping document will unavoidably be checked at flush time. If we really wanted to let the
user select the lock strategy, we'd have to provide two different jars, with and
without version columns.
Select the Lock Strategy in jbpm.cfg.xml
----------------------------------------
Key: JBPM-1953
URL: https://jira.jboss.org/jira/browse/JBPM-1953
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Core Engine
Reporter: Thomas Diesler
Assignee: Alejandro Guizar
Priority: Critical
Fix For: jBPM 3.3.2 GA
A StaleObjectStateException is thrown by Hibernate so easily, if the number of
JobExceutor's thread is two or more. If you set the number of thread to
./samples/quickstarts/bpm_orchestration2,
you could see the issue easily.
For a complete description, see the (private) document attached to JBPM-1952
--
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