Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1052299

Summary: Rule from older Jar is fired together with rule from new version of Jar
Product: [Retired] JBoss BRMS Platform 6 Reporter: Tomas David <tdavid>
Component: BREAssignee: Mario Fusco <mfusco>
Status: CLOSED CURRENTRELEASE QA Contact: Tomas David <tdavid>
Severity: medium Docs Contact:
Priority: urgent    
Version: 6.0.0CC: atangrin, etirelli, mbaluch
Target Milestone: ER1   
Target Release: 6.0.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 19:57:51 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:
Embargoed:
Attachments:
Description Flags
Test reproducer. none

Description Tomas David 2014-01-13 15:33:16 UTC
Created attachment 849449 [details]
Test reproducer.

Description of problem:
When new version of jar is deployed, kieScanner.scanNow is called, kieSession is created from kieContainer and fireAllRules is called, rule from older Jar is fired together with rule from new version of Jar.

Test is similar to testScannerOnPomProject from KieRepositoryScannerTest (pom project has dependency to artifact), but jars contains only rules returning its name.

Version-Release number of selected component (if applicable):
Drools 6.0.0-SNAPSHOT
Drools 6.0.0.ER7

How reproducible:
Test in attachment.

Steps to Reproduce:
1. Copy text of test from attachement to KieRepositoryScannerTest in drools.
2. Run test.

Actual results:
Rules from both jars are fired.

Expected results:
Only the newest rule should fire.

Additional info:

Comment 1 Mario Fusco 2014-01-14 15:34:45 UTC
Fixed by https://github.com/droolsjbpm/drools/commit/bbd1c28f7

Comment 2 Tomas David 2014-02-18 14:21:32 UTC
Verified on BRMS 6.0.1.ER1.