Bug 1040032

Summary: Drools goes into infinite loop in stateful mode with specific rule that uses exist
Product: [Retired] JBoss BRMS Platform 6 Reporter: Geoffrey De Smet <gdesmet>
Component: BREAssignee: Mario Fusco <mfusco>
Status: CLOSED CURRENTRELEASE QA Contact: Tomas Schlosser <tschloss>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.0CC: etirelli, mwinkler, rrajasek, rzhang
Target Milestone: ER 7   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 20:19: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:
Attachments:
Description Flags
isolated reproducer none

Description Geoffrey De Smet 2013-12-10 14:54:00 UTC
Created attachment 834808 [details]
isolated reproducer

I reproduced 2 different things going wrong in the Drools rule engine in stateful mode with PHREAK:
- infinite loop (which takes up 100% of 1 cpu power core)
- NPE deep inside drools.

But Mario and I believe they have the same cause.

I've isolated a small reproducer that reproduces the issue via OptaPlanner, with only 4 entities, 4 moves, 1 step and 1 score rule. It's attached to this issue.
This normally enables Mario to find the cause and fix it, as we did in the past for many PHREAK bugs.

Comment 4 Mario Fusco 2013-12-12 16:54:03 UTC
Fixed by https://github.com/droolsjbpm/drools/commit/a7162dfd3

Comment 5 JBoss JIRA Server 2013-12-13 09:09:51 UTC
Geoffrey De Smet <ge0ffrey.spam> updated the status of jira PLANNER-163 to Resolved

Comment 6 Tomas Schlosser 2014-01-15 11:14:08 UTC
Verified with BRMS 6.0.1-redhat-2