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

Avoid acquiring a kbase readlock when performing a working memory action

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Major Major
    • 6.4.0.Final, 7.0.0.Final
    • None
    • None
    • None
    • NEW
    • NEW

      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.

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

                Created:
                Updated:
                Resolved: