[
https://jira.jboss.org/jira/browse/JBPM-1757?page=com.atlassian.jira.plug...
]
Tom Baeyens commented on JBPM-1757:
-----------------------------------
probably it is just the example that is not completely implemented.
the example should try an operation and retry in case a SOSE comes out of the transaction
reporting an optimistic locking exception. probably this error report is indicating that
the example doesn't have this retry behaviour.
this should be fixed by using the full service-command based infrastructure in jbpm 4.
StaleObjectStateException and Rollback in Join- Node
-----------------------------------------------------
Key: JBPM-1757
URL:
https://jira.jboss.org/jira/browse/JBPM-1757
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Engine
Affects Versions: jBPM 3.2.3
Environment: Mac Osx 10.5.5, JBoss AS 4.2.3 GA, jbpm-jpdl-3.2.3-suite, Oracle 10g
Express Server 1.1
Reporter: Rainer Buss
Assignee: Alejandro Guizar
Attachments: ContinueActionHandler.java, error_log.txt,
error_log_wo_sql_trace.txt, SimpleFork.jpdl.xml
Executing a test process inside JBoss 4.2.3 using jbpm-enterprise.ear throws
StaleObjectStateException in Join- node. The process consists of two nodes with async =
true between fork and join. Please see process- defintion and action- handler in the
referenced forum entry. The rollback causes one node action to be executed twice.
Modifications of the distributed ear: I customized the ear by changing the property
'hibernate.dialect' to 'Oracle9iDialect' in hibernate.cfg.xml. As
transaction factory I tried JTATransactionFactory as well as CMTTransactionFactory,
without change of behaviour in this case. File jbpm.cfg.xml I kept unchanged.
(Setting the node attributes to async=false the instance is processed without error)
I will attach a log with and without sql- tracing.
In my opinion the issue is not dependent on using oracle, because I had the same effect
with the preinstalled hsqldb.
--
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