[jboss-jira] [JBoss JIRA] (DROOLS-1110) Avoid acquiring a kbase readlock when performing a working memory action

[Mario Fusco (JIRA)]

     [ https://issues.jboss.org/browse/DROOLS-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mario Fusco closed DROOLS-1110.
-------------------------------
    Fix Version/s: 6.4.0.Final
                   7.0.0.Final
       Resolution: Done


Implemented by https://github.com/droolsjbpm/drools/commit/1e50f13e6

> Avoid acquiring a kbase readlock when performing a working memory action 
> -------------------------------------------------------------------------
>
>                 Key: DROOLS-1110
>                 URL: https://issues.jboss.org/browse/DROOLS-1110
>             Project: Drools
>          Issue Type: Enhancement
>            Reporter: Mario Fusco
>            Assignee: Mario Fusco
>             Fix For: 6.4.0.Final, 7.0.0.Final
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)