[jboss-jira] [JBoss JIRA] (DROOLS-1110) Avoid acquiring a kbase readlock when performing a working memory action
RH Bugzilla Integration (JIRA)
issues at jboss.org
Tue Apr 12 08:33:00 EDT 2016
[ https://issues.jboss.org/browse/DROOLS-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190502#comment-13190502 ]
RH Bugzilla Integration commented on DROOLS-1110:
-------------------------------------------------
Mario Fusco <mfusco at redhat.com> changed the Status of [bug 1326329|https://bugzilla.redhat.com/show_bug.cgi?id=1326329] from NEW to ASSIGNED
> 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)
More information about the jboss-jira
mailing list