Bug 724344 (BRMS-290) - Allow user-configured maxRuleFirings in test scenarios
Summary: Allow user-configured maxRuleFirings in test scenarios
Keywords:
Status: NEW
Alias: BRMS-290
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: unspecified
Version: 5.0.1
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: future
Assignee: trev
QA Contact: Jiri Locker
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-31 19:18 UTC by Tihomir Surdilovic
Modified: 2021-02-16 02:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Feature Request


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-290 0 Major Closed Allow user-configured maxRuleFirings in test scenarios 2013-08-14 15:57:23 UTC

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



Note You need to log in before you can comment on or make changes to this bug.