[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...
]
Mark Little commented on JBPM-1953:
-----------------------------------
We are not going to configure the transaction manager to suppress warnings. The TM is
correct in giving this warning and it does not have the necessary semantic information to
disambiguate this Synchronization from a one that is really in error. The issue should be
dealt with by the participant.
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