[jbpm-issues] [JBoss JIRA] Updated: (JBPM-2087) Verify high volumn job executions with rollback

Verify high volumn job executions with rollback ----------------------------------------------- Key: JBPM-2087 URL: https://jira.jboss.org/jira/browse/JBPM-2087 Project: JBoss jBPM Issue Type: Task Components: Core Engine Reporter: Thomas Diesler Fix For: jBPM 4.0.x Use JMS instead of DBMS for the store of Jobs. In this case, a Job is not taken by multi-JobExecutors completely. The configration is mentioned by jBPM Reference Guide in SOA Platform. http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.GA/html-single/JB... --- Discussion Summary --- There are two separate places where locking is an issue. * Job acquisition * Join node The join node already supports pessimistic locking, whereas job acquisition *under the job executor* does not. On the other hand, under JMS, job acquisition does not exhibit any locking issue because each job is a separate message. The container deals with distributing the messages among the pool of JobListenerBean instances. Using JMS will remove the clashes, at least from the perspective of the job executor. Supporting the JMS feature negates the need for pessimistic locking during job acquisition. Given the above points, if JBPM-1952 is fully supported then JBPM-1953 becomes unnecessary.