[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...
]
Martin Putz commented on JBPM-1953:
-----------------------------------
"Issue2:
Workaround: Don't use ESB node in Fork/Join using jPDL."
==> To get around StaleObjectStateExceptions when entering a Join on certain databases
(postgres, oracle), jBPM 3.3.x allows to alter the locking strategy of the parent token
(see JBPM-1886).
A quick test of running the bpm_orchestration2 quickstart (DB=postgres, nbrOfThreads=2,
jBPM 3.3.0.GA) with a different locking strategy (<join name="join1"
lock="READ">) resulted in successful runs without any errors.
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