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

SessionStats eventsMatched isn't correctly calculated in case of match_multiple_rules

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • Ansible Integration
    • None
    • 2023 Week 36-38 (from Sep 4)
    • NEW
    • NEW
    • ---
    • ---

      Issue Description:

      When match_multiple_rules is true, SessionStats.eventsMatched returns 0.

      For example, MultipleRuleMatchTest.processEventsWithMatchMultipleRules_shouldMatchMultipleRules

      2023-10-06 18:20:58:394 +0900 [main] INFO org.drools.ansible.rulebook.integration.api.RulesExecutor - Disposing session with id: 1; SessionStats{start='2023-10-06T09:20:58.284042115Z', end='2023-10-06T09:20:58.372064748Z', lastClockTime='2023-10-06T09:20:58.286Z', clockAdvanceCount=0, numberOfRules=2, numberOfDisabledRules=0, rulesTriggered=2, eventsProcessed=1, eventsMatched=0, eventsSuppressed=1, permanentStorageCount=1, permanentStorageSize=20, asyncResponses=0, bytesSentOnAsync=0, sessionId=1, ruleSetName='null', lastRuleFired='R2', lastRuleFiredAt='2023-10-06T09:20:58.286Z'}
      

      Acceptance Criteria:

      • Fix eventsMatched and add assertions to the test case

              rhn-support-tkobayas Toshiya Kobayashi
              rhn-support-tkobayas Toshiya Kobayashi
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: