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

Bug 1163965

Summary:	Multiple RuntimeEngines not getting disposed
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Alessandro Lazarotti <alazarot>
Component:	jBPM Core	Assignee:	Alessandro Lazarotti <alazarot>
Status:	CLOSED EOL	QA Contact:	Ivo Bek <ibek>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.0.2	CC:	ibek, kverlaen, mbaluch, rzhang
Target Milestone:	---
Target Release:	One-off release
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1175901 (view as bug list)		Environment:
Last Closed:	2020-03-27 20:09:48 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:
Bug Depends On:
Bug Blocks:	1163975, 1175901

Description Alessandro Lazarotti 2014-11-13 19:50:48 UTC

Platform BZ for https://issues.jboss.org/browse/JBPM-4439

----------------------------------------------------------

Multiple RuntimeEngines are not disposed properly when created in the same Transaction. When a RuntimeEngine is created there is a transaction synchronization (DisposeSessionTransactionSynchronization) created to dipose it after the transaction commits. All instances of DisposeSessionTransactionSynchronization are identical according to their compareTo method, which is what the TransactionSynchronizationContainer uses when storing them. So only one synchronization gets stored and when the transaction commits there are stale runtime engines present.

Comment 2 Maciej Swiderski 2014-11-14 11:23:12 UTC

commits backported to 6.0.x branch

drools:
6.0x:
https://github.com/droolsjbpm/drools/commit/2f092e1a4821abef76521a87399398a6e3e99bc8

jbpm
6.0.x:
https://github.com/droolsjbpm/jbpm/commit/b753d4c3337e6a41399f046966ebef85f9ca0ed2

Comment 8 Jiri Svitak 2015-01-13 11:52:41 UTC

This bugzilla was target to a one-off patch and was verified by Ivo, see #c3.

Setting to verified status and updating its target release to one-off.

Bugzilla which tracks the fix in 6.1 is BZ1142943 (also mentioned in "See also" section).
Bugzilla which tracks the fix in 6.0.3 rollup patch #2 is BZ1175901.