[
http://jira.jboss.com/jira/browse/JBPM-983?page=comments#action_12367428 ]
Jan-Philipp Bolle commented on JBPM-983:
----------------------------------------
Thank you, Edward, for your support.
In our project we solved the problem for our needs. It's not a good solution but it
seems to work.
-First we created a single thread how to select the jobs and to distribute the work to
free threads.
-Then we removed the restart functionality.
-We always synchronise the jobexecution with nodeID and prozessID. This only works if you
use async in a join node and doesn't use subprocesses.
-To solve the problems with subprocesses we add a dummynode before finishing and set this
to exclusive. In the Jobexecution we synchronise all threads which are marked as
exclusive.
-Then the last problem was by starting a new thread directly after the next with the same
process we got an exception. We solved this problem by waiting a second after the
execution.
It's really dirty but it works.
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