[jbpm-issues] [JBoss JIRA] Commented: (JBPM-1886) Oracle causing StaleObjectStateException
[
https://jira.jboss.org/jira/browse/JBPM-1886?page=com.atlassian.jira.plug...
]
Martin Putz commented on JBPM-1886:
-----------------------------------
As discussed in the forums -
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=147330 - a possible
workaround to avoid the StaleObjectStateException in the case of a direct transition from
fork to join in one of the branches is to explicitly change the lock mode on the join:
<join name="foo" lock="UPGRADE">
This results in a pessimistic lock, where the version on the parent token is not
incremented. It might need further investigations if this has other drawbacks, but the
test case shown in the forum thread runs through fine with this setting.
Oracle causing StaleObjectStateException
----------------------------------------
Key: JBPM-1886
URL: https://jira.jboss.org/jira/browse/JBPM-1886
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Engine
Affects Versions: jBPM 3.3.0 GA
Environment: JBoss 4.2.2, JBPM 3.3.0.GA, Oracle 10
Reporter: Petr Nejedly
Fix For: jBPM 3.3.2 GA
Getting StaleObjectStateException when creating and running a process via Oracle DB.
Looks like this has been solved before ( JBPM-1085 ) but a call to session.flush() has
been removed later ( JBPM-1772 ).
--
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