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

[ed] when a ProcessState is completed on a job that started in the subprocess, a collision can occur with another thread concurrently running in the parent process, resulting in a StaleObjectStateException

[tom]: i don't really get this problem. and then i don't see why the staleobjectexception is a problem. that is to be expected when 2 independent threads operation on the same process instance runtime information item, no ?

[ed] The limitation in this case is that it is invalid to use a subprocess on a fork that may complete while active execution is happening on another branch of the fork. Is that what you mean to say? How, in practice, are you thinking that people would be able to use subprocesses on forks with this limitation? 

[tom]  i still didn't get the problem.  i'm looking for the scenario where things go wrong.  maybe it is easiest if you can help me get the test going in the code base: jpdl/jar/src/main/java/org/jbpm/job/executor/ConcurrencyTest.java  then it might be easier to help me reproduce and see the problem

> 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