[jboss-jira] [JBoss JIRA] Created: (JBRULES-3044) Need BRMS-586/590 hotfix for Drools 5.1.1 / Salience firing order reversed or not observed on multple fact inserts post index

[Armand Welsh (JIRA)]

Need BRMS-586/590 hotfix for Drools 5.1.1 / Salience firing order reversed or not observed on multple fact inserts post index
-----------------------------------------------------------------------------------------------------------------------------

                 Key: JBRULES-3044
                 URL: https://issues.jboss.org/browse/JBRULES-3044
             Project: Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-compiler, drools-core
    Affects Versions: 5.1.1.FINAL
         Environment: Windows 7/64, ReHat Enterprise Linux 6, Drools 5.1.1 running Java 6 JRE/SDK (all versions currently available from Oracle), 2 GB RAM, 20+ GB Free HD Space
            Reporter: Armand Welsh
            Assignee: Mark Proctor
            Priority: Critical
             Fix For: 5.1.1.FINAL


When executing fireAllRules, all pre-index rules fire adhering to the salience prioritization.  If, however, during post-index execution, facts are inserted that are used in the conditions of lower salience rules in the same activation group, the rule will fire, regardless of the fact a higher salience rule has already fired.

This is further complicated when defining default rules of default salience (though any salience value will suffice so long as the default rule has the lowest salience within the activation group).  When no pre-indexed facts are availble for the activation group, the default rule fires.  along, with other activation group rules.  During execution, a new fact is inserted that provides a hit for a higher salience rule in the same activation group as the default rule which already fired, however, the rule is not fired.

In effect, pre-indexed facts are processed in descending salience order.  whereas post-indexed facts are processed in ascending salience order.

In all scenarios described, there is not a fire once restriction assigned.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira