[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_12375588 ] 
            
Tom Baeyens commented on JBPM-983:
----------------------------------

"
Remember, in the failure scenario the subprocess has passed an async node, so it's running on a "new" thread. If it completes very quickly, the calling token may not yet be saved, resulting in a SOSException on the token.
"

this is also due to the isolation level 0.  but even in most of those cases you just get an SOSException and there is no problem.  in that case, the tx rolls back, which means that the message was not consumed and it will be processed again.    as long as the database executes the updates atomically, there is no problem.  

"
job-posting is not performed as part of the overall JBPM transaction, because it's on a separate Hibernate session. Correct? 
"

No.  Jobs are inserted in the same transaction as the process updates.  That is important.

"
This may seem like a bizarre scenario - who would call a subprocess that immediately returns? 
"

use case is valid

> 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