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

Reentrant working memory actions aren't flushed immediately even when eager evaluation is forced

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 6.4.0.CR2, 7.0.0.Final
    • None
    • None
    • None

    Description

      jBPM requires Drools working memory actions to be immediately flushed and then uses Drools force eager activation option. However even when this option is enabled working memory actions that aren't created in a reentrant way (during a rule firing) are enqueued instead of being flushed as expected by jBPM.

      Attachments

        Activity

          People

            mfusco@redhat.com Mario Fusco
            mfusco@redhat.com Mario Fusco
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: