Bug 1040032 - Drools goes into infinite loop in stateful mode with specific rule that uses exist
Summary: Drools goes into infinite loop in stateful mode with specific rule that uses ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: BRE
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER 7
: 6.0.0
Assignee: Mario Fusco
QA Contact: Tomas Schlosser
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-10 14:54 UTC by Geoffrey De Smet
Modified: 2014-08-06 20:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:19:41 UTC
Type: Bug

Attachments (Terms of Use)
isolated reproducer (3.94 MB, application/x-gzip)
2013-12-10 14:54 UTC, Geoffrey De Smet 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker PLANNER-163 0 Major Resolved Benchmarker runs forever (because of infinite loop in drools or optaplanner) 2014-01-15 11:14:14 UTC

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
Note You need to log in before you can comment on or make changes to this bug.