Bug 1142943 - Multiple RuntimeEngines not getting disposed-JBPM-4439
Summary: Multiple RuntimeEngines not getting disposed-JBPM-4439
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Core
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER2
: 6.1.0
Assignee: Alessandro Lazarotti
QA Contact: Marek Baluch
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-17 15:56 UTC by Gary Hu
Modified: 2020-03-27 20:04 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:04:05 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1163965 0 high CLOSED Multiple RuntimeEngines not getting disposed 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1175901 0 high CLOSED [6.0.3.RP#2] Multiple RuntimeEngines not getting disposed 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker JBPM-4439 0 Major Resolved Multiple RuntimeEngines not getting disposed 2017-02-06 12:34:05 UTC

Internal Links: 1163965 1175901

Description Gary Hu 2014-09-17 15:56:20 UTC 
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.

There's a jira already opened for this issue and a fix is already created [1]

Can we push this fix to the next release?

[1] https://github.com/droolsjbpm/jbpm/commit/284a8018072000d8cfae40348dd6778241aeaf19
Comment 2 Kris Verlaenen 2014-09-18 14:38:14 UTC 
Setting to MODIFIED as the fix is already upstream.
Comment 4 Jiri Svitak 2014-11-21 13:30:16 UTC 
Verified in BPMS 6.1.0.ER2.

The test is implemented in QE regression suite:
https://gitlab.mw.lab.eng.bos.redhat.com/bxms/brms/commit/cf4a8a00b0b63104e92e3e4248ff5ab9181fb0ef
as BZ1163965MultipleRuntimeEngineTest.
Note You need to log in before you can comment on or make changes to this bug.