Bug 980466 – Live queries are not live when fireAllRules() is not called

Bug 980466 - Live queries are not live when fireAllRules() is not called

Summary:	Live queries are not live when fireAllRules() is not called

Status:	CLOSED NOTABUG

Aliases:	None

Product:	JBoss BRMS Platform 6
Classification:	JBoss
Component:	BRE (Show other bugs)
Sub Component:
Version:	6.0.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity high
Target Milestone:	ER2
Target Release:	6.0.0
Assigned To:	Mario Fusco
QA Contact:	Marek Winkler
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2013-07-02 09:05 EDT by Marek Winkler
Modified:	2013-09-02 06:54 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2013-09-02 06:54:06 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Marek Winkler 2013-07-02 09:05:54 EDT

Description of problem:

With Phreak, live queries require calling fireAllRules() to produce correct results. This is quite confusing, has it been designed to work this way?

If this behaviour was not anticipated, and this is really a bug, I will attach a reproducer.

Version-Release number of selected component (if applicable):

Drools 6.0.0-SNAPSHOT
Drools 6.0.0.Beta4

Comment 1 Mario Fusco 2013-08-05 13:06:25 EDT

This is how phreak is expected to work. The correct way to use this, is to setup a Runnable that calls fireAllRules every x seconds. This is a performance related aspect too, as it also allows the engine to exploit batching and the user to get control of the regularity of the batch eval.

Comment 2 Marek Winkler 2013-09-02 06:54:06 EDT

Confirmed that this is the expected behaviour.

Note You need to log in before you can comment on or make changes to this bug.