Bug 1012933
| Summary: | Stream mode with CR4-Pre1 generates rules looping | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Richard Bourner <rbourner> | ||||
| Component: | BRE | Assignee: | Mario Fusco <mfusco> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tomas David <tdavid> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 6.0.0 | CC: | ddoyle, etirelli, omikelad, rbourner | ||||
| Target Milestone: | ER5 | ||||||
| Target Release: | 6.0.0 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-08-06 20:17:41 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: |
|
||||||
Richard Bourner <richard> made a comment on jira DROOLS-276 A little precision: it appears that the problem occurs only with Phreak algo in Stream mode. In the unit test I created, I had not included the reteoo JAR, so it was redirected to Phreak without my noticing. Bottom line: out of 4 unit tests, only 1 fails now. A little precision: it appears that the problem occurs only with Phreak algo in Stream mode. In the unit tests I created, I had not included the reteoo JAR, so it was redirected to Phreak without my noticing. Bottom line: out of 4 unit tests, only 1 fails now. Mario Fusco <mario.fusco> updated the status of jira DROOLS-276 to Resolved Verified on BRMS 6.0.0.ER5. |
Created attachment 803925 [details] Maven Eclipse project demonstrating the issue Description of problem: When in STREAM mode our rules are looping because of an update. The attached example doesn't demonstrate the looping but one rule is fired twice where it should only fire once. We are supposing that the issue is the same. Version-Release number of selected component (if applicable): Drools 6.0.0.CR4-Pre1 How reproducible: Run the unit test in the attached Maven Eclipse project. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: