Bug 1318053

Summary: [GSS](6.2.z) Rules with activation-group firing not exclusivaly
Product: [Retired] JBoss BPMS Platform 6 Reporter: Alessandro Lazarotti <alazarot>
Component: BREAssignee: Mario Fusco <mfusco>
Status: CLOSED EOL QA Contact: Ivo Bek <ibek>
Severity: unspecified Docs Contact:
Priority: urgent    
Version: 6.2.0CC: etirelli, ibek, kverlaen, mwinkler, rrajasek
Target Milestone: CR1   
Target Release: 6.2.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1318052 Environment:
Last Closed: 2020-03-27 19:12:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1318052    
Bug Blocks: 1327763, 1327765    
Attachments:
Description Flags
reproducer-junit none

Description Alessandro Lazarotti 2016-03-15 21:44:10 UTC 
+++ This bug was initially created as a clone of Bug #1318052 +++

Description of problem:

For some scenario activation-group is not working properly.
It seems related with Not Nodes.

I am attaching a simple reproducer where two rules in the same activation-group are fired where only one is expected. 

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

How reproducible:
Always

Steps to Reproduce:
1. run the attached maven project


Actual results:
Two rules are fired

Expected results:
Only one is expected
Comment 2 Alessandro Lazarotti 2016-03-15 21:56:51 UTC 
Created attachment 1136781 [details]
reproducer-junit
Comment 3 Mario Fusco 2016-04-18 08:56:25 UTC 
Cherry-picked to 6.3.x branch with https://github.com/droolsjbpm/drools/commit/29e1f0d0b
Comment 4 Ivo Bek 2016-05-04 11:03:24 UTC 
Verified in BPM Suite 6.2.3.CR1

The test ActivationTest passed.