Bug 743150 - Task functionality does not allow for concurrency
Summary: Task functionality does not allow for concurrency
Keywords:
Status: NEW
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: jBPM 5
Version: BRMS 5.3.0.GA
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Kris Verlaenen
QA Contact: Radovan Synek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-04 02:44 UTC by Jeffrey Bride
Modified: 2022-01-05 05:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.