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

Avoid acquiring a kbase readlock when performing a working memory action

    Details

    • Type: Enhancement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 6.4.0.Final, 7.0.0.Final
    • Component/s: None
    • Labels:
      None
    • Docs QE Status:
      NEW
    • QE Status:
      NEW

      Description

      At the moment all working memory actions (insert/update/delete) need to acquire a read lock on the kbase. This is avoidable making the kbase to deactivate (through their state machine) all the ksessions created from it before modifying the kbase itself.

        Gliffy Diagrams

          Attachments

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: