Description of problem: If the first rule to fire in a session modifies a fact, the engine improperly cancels pending activations depending on that fact. Version-Release number of selected component (if applicable): 5.3.0 How reproducible: A test case where the first rule to fire modifies a fact that previously activated other rules. Actual results: Activations improperly cancelled Expected results: Activations are not cancelled and fire properly. Additional info: This was raised by a partner. The actual details/rules are confidential and shared under NDA. I am opening this ticket for the partner.
This bug occurs only in a very specific scenario, but it is very critical as it silently fails causing the engine to produce wrong results.
Fix backported to 5.3.x.
The test case to reproduce and verify this problem is committed here: https://github.com/droolsjbpm/drools/commit/e80ed64d621ec5d4671147cc400e857e652578a7 Please note that the scenario is very specific, so even changing the order of the updates on the consequence will prevent the bug from showing up.
I have updated the Doc Text for documentation Release Notes. Thank you for the information. - Doug
Verified on 5.3.1.BRMS-ER4.
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.