[jboss-jira] [JBoss JIRA] (JBRULES-3677) Duplicated main agenda group on session reset

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/JBRULES-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731151#comment-12731151 ] 

RH Bugzilla Integration commented on JBRULES-3677:
--------------------------------------------------

Maciej Swiderski <mswiders at redhat.com> made a comment on [bug 872548|https://bugzilla.redhat.com/show_bug.cgi?id=872548]

Description of problem:


In case knowledge session is reset (for instance due to transaction rollback) main agenda group is duplicated. First time is added by clear method in DefaultAgenda and then right after by the marshaller

Consequence of it is that rules are not fired after session reset.

This is a backport of jira JBRULES-3677

Version-Release number of selected component (if applicable):


How reproducible:
See bz https://bugzilla.redhat.com/show_bug.cgi?id=862296 for all steps that needs to be taken to reproduce it. That bz was about transactions but revealed problem with handling rule tasks in the processes

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
                
> Duplicated main agenda group on session reset
> ---------------------------------------------
>
>                 Key: JBRULES-3677
>                 URL: https://issues.jboss.org/browse/JBRULES-3677
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-core
>    Affects Versions: 5.3.0.Final
>            Reporter: Maciej Swiderski
>            Assignee: Mario Fusco
>
> In case knowledge session is reset (for instance due to transaction rollback) main agenda group is duplicated. First time is added by clear method in DefaultAgenda and then right after by the marshaller
> Consequence of it is that rules are not fired after session reset.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira