Bug 1190923

Summary: Although user update some facts and re-calculation in the accumulate condition is proceeded, rule won't be fired.
Product: [Retired] JBoss BRMS Platform 6 Reporter: Hisao Furuichi <hfuruich>
Component: BREAssignee: Mario Fusco <mfusco>
Status: CLOSED EOL QA Contact: Marek Winkler <mwinkler>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.3CC: alazarot, etirelli, mfusco
Target Milestone: ER5Flags: hfuruich: needinfo+
Target Release: 6.1.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:08:30 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:
Attachments:
Description Flags
reproducer none

Description Hisao Furuichi 2015-02-10 02:12:47 UTC
Created attachment 989915 [details]
reproducer

Description of problem:
Although user update some facts and re-calculation in the accumulate condition is proceeded, rule won't be fired.  Using "collect" instead of "accumulate" does not work either.  When we comment out "no-loop true" and "update($target)", the rule is fired correctly, but that modification won't be propagated because it was not notified to the engine.  If we use "simple" conditions (without accumulate nor collect), it works fine.

Version-Release number of selected component (if applicable):
- BRMS 6.0.3
- BRMS 6.1.0.ER4

Steps to Reproduce:
1. Download attached reproducer and run JUnit Test written in com.sample.DroolsTest

Actual results:
Fail the Junit test. (Rule is not fired when user update some facts and re-calculation in the accumulate condition is proceed)

Expected results:
Pass the JUnit test.(Rule is fired when user update some facts and re-calculation in the accumulate condition is proceed)

Comment 3 Mario Fusco 2015-02-11 09:41:42 UTC
This issue has been already reported (in a slightly different way) here https://issues.jboss.org/browse/DROOLS-694 and fixed with this commit https://github.com/droolsjbpm/drools/commit/1484c4fb91b586ae9465ec324304129af0d243ce

I checked that the provided reproducer now works on both master and 6.2.x branches.

Comment 4 Edson Tirelli 2015-02-11 15:06:12 UTC
Setting the target milestone and target release to be included in ER5 testing.

Comment 7 Marek Winkler 2015-03-05 12:35:47 UTC
Verified in BRMS 6.1.0 ER5.