Created attachment 828572 [details] Some code to demonstrate the issue. Description of problem: If you have a rule with both noloop and update where there are multiple matches on the LHS, the RHS only runs for first match instead of running for all matches. This is completely different to the behaviour under 5.3 and will break lots of existing code. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Build the attached code against BRMS6.0 and run - test will fail 2. Build the code against BRMS5.3 and the test will pass ...OR... 2. Or remove the uodate($order) call from the RHS under BRMS6.0 and the test will pass Actual results: Evaluation of the RHS stops after the update call Expected results: The RHS should be evaluated for all matches Additional info:
Fixed by https://github.com/droolsjbpm/drools/commit/a558125a2
Verified on BRMS-6.0.0.ER7
qe_test_coverage: covered by community unit tests