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

Bug 1247913

Summary:	FireUntilHalt should throw UnsupportedOperationException when called from KieSession from RuntimeEngine
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Tibor Zimanyi <tzimanyi>
Component:	BRE	Assignee:	Edson Tirelli <etirelli>
Status:	CLOSED EOL	QA Contact:	Tibor Zimanyi <tzimanyi>
Severity:	low	Docs Contact:
Priority:	medium
Version:	6.1.0	CC:	kverlaen
Target Milestone:	ER3
Target Release:	6.2.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:05: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 Tibor Zimanyi 2015-07-29 08:39:39 UTC

Description of problem: 

When fireUntilHalt is called from KieSession that is obtained from RuntimeEngine, no rules are fired. According to BZ [1], using fireUntilHalt in jBPM engine is not a valid use case, so it should throw UnsupportedOperationException or something similar, so the user is informed, that he should not use it. See [1] for more info. 

How reproducible: Run test from this paste [2]

Additional info:

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1218291
[2] http://pastebin.com/t40cS285

Comment 2 Maciej Swiderski 2015-09-08 12:49:13 UTC

it does work ok when using singleton runtime manager only as it does keep the ksession active so it can be used. enabled tests in jbpm-test-coverage that proves it and is same as linked in this bs

jbpm
master:
https://github.com/droolsjbpm/jbpm/commit/ab41cdee03b421d741775c0cdf0f15ca419eab8c

6.3.x:
https://github.com/droolsjbpm/jbpm/commit/2dcaf21d724d251e013870bc356eee509ef8c56e

Comment 3 Tibor Zimanyi 2015-10-07 11:49:18 UTC

Verified. The test passes. Is this somewhere documented? I think we should document this behavior if we don't have it documented yet (only singleton runtime manager when using fireUntilHalt).