Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1191285

Summary:	Blocking on TaskTransactionInterceptor
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Marco Rietveld <mrietvel>
Component:	Business Central	Assignee:	Marco Rietveld <mrietvel>
Status:	CLOSED EOL	QA Contact:	Marek Baluch <mbaluch>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.1.0	CC:	kverlaen, mbaluch, smcgowan
Target Milestone:	ER6
Target Release:	6.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-27 20:06:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Marco Rietveld 2015-02-10 22:45:52 UTC

Description of problem:

The problem is that Human Task related operations via the Remote API (REST or JMS) end up blocking because of a shared object TaskService instance (between all requests). 

How reproducible:



Steps to Reproduce:
1. Run a performance test involving concurrent task-related remote requests
2.
3.

Actual results:

In JBPM-4547, the user reports that the average time is 30 seconds per request. 

Expected results:

Faster than this. 

Additional info:

The cause for this, an unforeseen combination of the TaskService architecture and the kie-wb/business-central CDI architecture, has already been identified.

Comment 1 Maciej Swiderski 2015-02-19 13:31:39 UTC

fixed on master, another fix for 6.0.x (that this bug was originally filed against) is ready as well.

jbpm
master:
https://github.com/droolsjbpm/jbpm/commit/0a2af06add50d2a78e258ffbd95c77019d969c55

if that shall be back ported to 6.2.x please assign this back to me as it has not all flags acks.
same thing when 6.0.x fix should be applied - it does have different change not in jbpm but in droolsjbpm-integration)

Comment 2 Kris Verlaenen 2015-02-20 12:52:49 UTC

Assigned again for backport.

Comment 3 Maciej Swiderski 2015-02-20 13:04:31 UTC

backported to 6.2.x:

jbpm
6.2.x:
https://github.com/droolsjbpm/jbpm/commit/8953ff7a18ca86c0e4e86741460c992437112184

Comment 4 JBoss JIRA Server 2015-02-20 13:13:35 UTC

Maciej Swiderski <swiderski.maciej> updated the status of jira JBPM-4547 to Resolved

Comment 5 Jiri Svitak 2015-03-18 13:11:09 UTC

Maciej,
Thank you for pointing me to a reproducer [1].

I reproduced the problem in BPMS 6.0.3.GA using the provided scenario.
I could see ten BLOCKED threads containing TaskTransactionInterceptor, I used ten client threads.

I have tested this with BPM Suite 6.1.0.ER6 and the problem is fixed. I could see only one thread with TaskTransactionInterceptor instance in status RUNNABLE.

Verified in BPM Suite 6.1.0.ER6.

[1] https://mojo.redhat.com/people/selrahal/blog/2015/02/04/load-testing-jbpm