[
http://jira.jboss.com/jira/browse/JBPM-974?page=comments#action_12363872 ]
Tom Baeyens commented on JBPM-974:
----------------------------------
the forum thread doesn't give my much to go on. the stack trace is a 'normal'
situation in a clustered environment. the idea is that the first transaction that commits
wins and the other one is rolled back. so the job should remain in the queue and get
picked up for execution again by the same thread for a next try.
please reopen if you have more concrete problem report. the job executor is tested witih
5 concurrent threads (but they are running on the same machine), which should not be a
problem.
concurrent job acquirement fails
--------------------------------
Key: JBPM-974
URL:
http://jira.jboss.com/jira/browse/JBPM-974
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2
Reporter: Alexander Schlett
Assigned To: Tom Baeyens
when more than 1 job executor thread is configured and concurrent async nodes are to be
executed, it results in hibernate exceptions.
reason: job acquirement is not synchronized well, resulting in multiple threads trying to
work on the same job.
--
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