Bug 743150

Summary: Task functionality does not allow for concurrency
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Jeffrey Bride <jbride2001>
Component: jBPM 5Assignee: Kris Verlaenen <kverlaen>
Status: NEW --- QA Contact: Radovan Synek <rsynek>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: BRMS 5.3.0.GACC: atangrin
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jeffrey Bride 2011-10-04 02:44:50 UTC
HornetQTaskServer consumes and processes messages serially and is subsequently a performance bottleneck.  

In addition, a locking mechanism has not been architected into org.jbpm.task.Task for isolation even if/when the HornetQTaskServer does allow for concurrency.

Comment 1 Tihomir Surdilovic 2011-10-07 13:30:18 UTC
Hi Jeffrey, could you give more details on this? Do you have a test case which shows this performance bottleneck?

Comment 3 Jeffrey Bride 2011-11-15 14:59:51 UTC
the following is a test case that demonstrates the problem :

https://github.com/jbride/jbpm/blob/gbd/jbpm-human-task/src/test/java/org/jbpm/task/service/local/sync/BRMS_743150_Test.java

Comment 4 Jeffrey Bride 2012-01-04 19:28:30 UTC
disregard above test case as it relates to race conditions with the jbpm5 Task and TaskServiceSession classes.  Will open a new issue that is specific to race conditions with task functionality

Will keep this issue open as it relates to the HornetqTaskServer architected as a single threaded MessageConsumer rather than, for example, a MDB.