[
http://jira.jboss.com/jira/browse/JBPM-983?page=comments#action_12371570 ]
Justin Zhou commented on JBPM-983:
----------------------------------
I am using oracle 10g. If set treecache isolation to serializable, fork/join works for me,
but not other levels. The problem is the treecache locking, looks like every transaction
will lock the whole cache tree from root, under heavy load, lock timeout can happen. Is
there anyway we can do lock a little smarter?
Will setting the datasource isolation level to serializable help? Unfortunately, I can not
do it with oracle XA datasource.
So my question is that is this a bug or just a database isolation level issue?
concurrent process execution fails
----------------------------------
Key: JBPM-983
URL:
http://jira.jboss.com/jira/browse/JBPM-983
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2
Environment: Hypersonic in-memory database, JobExecutor configured with 5
threads
Reporter: Alexander Schlett
Assigned To: Tom Baeyens
Priority: Critical
Fix For: jBPM 3.3
Attachments: SimpleTest.java, SimpleTest.java, SimpleTest.java, SimpleTest.java,
SimpleTest.java
concurrent execution of async nodes with multiple JobExecutor threads fails. the effect
is:
1) job sync within JobExecutor fails due to org.hibernate.StaleObjectStateException
2) process gets stuck in join node and never ends
junit test for this is attached, it's a simple process with just a fork and a join
and some scripts inbetween.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira