Bug 724344 (BRMS-290)

Summary: Allow user-configured maxRuleFirings in test scenarios
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Tihomir Surdilovic <tsurdilo>
Component: unspecifiedAssignee: trev <tkirby>
Status: NEW --- QA Contact: Jiri Locker <jlocker>
Severity: unspecified Docs Contact:
Priority: high    
Version: 5.0.1CC: gran
Target Milestone: ---   
Target Release: future   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/BRMS-290
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Tihomir Surdilovic 2010-03-31 19:18:37 UTC 
Date of First Response: 2010-04-01 12:31:29
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/708833
securitylevel_name: Public

Currently in org.drools.guvnor.client.modeldriven.testing.Scenario:

/**
     * The maximum number of rules to fire so we don't recurse for ever.
     */
    public int            maxRuleFirings = 100000;

in some development situations this number is way too high and costs system resources (when unwanted looping happens). It would be nice if maxRuleFirings was user-configurable per test-scenario (or per package which would affect all test scenarios in that package).
Comment 1 Tihomir Surdilovic 2010-04-01 16:09:57 UTC 
Probably better to assign Toni on this or Mic as it affects BRMS UI / Guvnor
Comment 2 Edson Tirelli 2010-04-01 16:31:29 UTC 
Assigning tickets to Toni as he handles BRMS issues AFAIK. I handle core/compiler/fusion issues.
Comment 3 Tihomir Surdilovic 2010-09-07 23:50:47 UTC 
Link: Added: This issue depends GUVNOR-619