Uploaded image for project: 'Drools'
  1. Drools
  2. DROOLS-4393

Expired events can be present in the collect result

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 7.24.0.Final
    • Fix Version/s: None
    • Component/s: core engine
    • Labels:
      None
    • Sprint:
      2019 Week 29-31, 2019 Week 32-34
    • Docs QE Status:
      NEW
    • QE Status:
      NEW

      Description

      Is there any option to expire the facts before fireAllRules()?

      A reproducer for drools 6.5.0.Final-redhat-25 (tested too on 7.23.0.Final-redhat-00002 and 7.24.0.Final) shows that facts are not expired until we run fireAllRules().

      Trying reproducer:

      Show facts are expired after fireAllRules():

      ```
      unzip -d reproducer reproducer-02425402.zip
      cd reproducer
      git checkout master
      ./run.sh
      ```

      Show facts are not expired before fireAllRules():

      ```
      git checkout original
      ./run.sh
      ```

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                mfusco Mario Fusco
                Reporter:
                afanjula Alberto Fanjul Alonso
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: