[jboss-jira] [JBoss JIRA] Commented: (JBPM-983) concurrent process execution fails

[Tom Baeyens (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBPM-983?page=comments#action_12375375 ] 
            
Tom Baeyens commented on JBPM-983:
----------------------------------

[tom]: isn't this due to your isolation level 0 ?

[ed] Yes. Are you saying that this should be a documented limitation also?

[tom]  that is what i'm saying.  we should document that better.  the problem is that i know READ_UNCOMMITTED is not good enough.  your scenario clearly illustrates that.  but i don't really know exactly what isolation level is needed.  i would guess read committed, but i'm not sure on all the implications of less-then-serializable transaction isolation.

> 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 jPDL 3.2.2
>
>         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