Backport the dispatcher thread from jBPM 4 to avoid race conditions with multiple JobExecutor threads ----------------------------------------------------------------------------------------------------- Key: JBPM-2959 URL: https://jira.jboss.org/browse/JBPM-2959 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.9, jBPM 3.2.8 Environment: - jBPM 3.2.8_SOA with multiple JobExecutor threads - MySQL 5.0.90 Reporter: Martin Putz Assignee: Alejandro Guizar Running two or more instances of the following test process leads to deadlock situations in MySQL when multiple JobExecutor threads are active: <process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="Process_Timer2"> <start-state name="start-state1"> <transition to="node1"></transition> </start-state> <state name="Sleep"> <timer duedate="1 seconds" name="sleep_timer_2" transition="OK" repeat="NO"> <action></action> </timer> <transition to="node1" name="OK"></transition> </state> <node name="node1"> <action class="Wait"></action> <transition to="Sleep"></transition> </node> </process-definition> The Wait class does nothing more than sleep for a second before continuing the execution: public void execute(ExecutionContext executionContext) throws Exception { Thread.sleep(1000); executionContext.leaveNode(); } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira