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

Thu Jun 28 14:05:58 EDT 2007

    [ http://jira.jboss.com/jira/browse/JBPM-983?page=comments#action_12367207 ] 

Edward Staub commented on JBPM-983:
-----------------------------------

Another report of related problems with asynchronous access to a not-yet-committed process instance can be found in http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008324#4008324.  In this case, an ActionHandler fires a JMS message, and the MDB tries to access the process instance before it's committed.

With the kind of fix described above, and if the message-firing node was marked "asynchronous", this problem would be resolved.  

AFAIK, no JIRA issue was filed.  "gforam" has not written about anything since, so I suspect he's dropped JBPM for one reason or another.

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