[jbpm-issues] [JBoss JIRA] Updated: (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 updated JBPM-1953:
-----------------------------------
Fix Version/s: (was: jBPM-3.2.5.SP1)
Without version checking, jobs get executed more than once. Even if selecting the lock
strategy with a switch was possible, the pessimistic strategy would not work under the
current job acquisition scheme.
No solution for JBPM-1953 can be provided soon enough to be included in 3.2.5 SP1, so I am
removing that version from the fix targets.
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.2.6 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