Bug 1175901 - [6.0.3.RP#2] Multiple RuntimeEngines not getting disposed
Summary: [6.0.3.RP#2] Multiple RuntimeEngines not getting disposed
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Core
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: One-off release
Assignee: Alessandro Lazarotti
QA Contact: Marek Baluch
URL:
Whiteboard:
Depends On: 1163965
Blocks: 1163975 1174357 1174359
TreeView+ depends on / blocked
 
Reported: 2014-12-18 20:45 UTC by Alessandro Lazarotti
Modified: 2020-03-27 20:10 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1163965
Environment:
Last Closed: 2020-03-27 20:10:32 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1142943 0 high CLOSED Multiple RuntimeEngines not getting disposed-JBPM-4439 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker JBPM-4439 0 Major Resolved Multiple RuntimeEngines not getting disposed 2016-08-10 15:49:13 UTC

Internal Links: 1142943

Comment 3 Jiri Svitak 2015-01-13 12:05:56 UTC 
Verified in BPM Suite 6.0.3 rollup patch #2.
(http://dev138.mw.lab.eng.bos.redhat.com/patches/BPMS_6.0.3_2_2014/)

Updating also target release to one-off and other flags. This BZ is part of the rollup patch #2 bugzilla, so here is the "Blocks" section the key.

Test coverage:
https://gitlab.mw.lab.eng.bos.redhat.com/bxms/brms/commit/cf4a8a00b0b63104e92e3e4248ff5ab9181fb0ef
Comment 4 Jiri Svitak 2015-01-13 12:09:48 UTC 
Btw the fix for 6.1 has been already verified here: BZ1142943. Added also to "See also" section.
Comment 6 Jiri Svitak 2015-01-14 16:59:30 UTC 
commits were already added as a part of previous one-off patch

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

jbpm
6.0.x:
https://github.com/droolsjbpm/jbpm/commit/b753d4c3337e6a41399f046966ebef85f9ca0ed2
Note You need to log in before you can comment on or make changes to this bug.