The usual reason would be that you have a rule which is updating a fact on which it has a constraint. After each update it is therefore re-evaluated. In which case, you just need to add "no-loop" to it.
Steve On 5 Sep 2013, at 10:47, Smurfs <[email protected]> wrote: > Hi > I am working on guvnor in jboss. > > I have created a simple test scenario to test a rule of quantity greater > than 5. When i run the scenario, it shows the message as "maximum number of > rule firings (100000) was reached. it is likely that there is a infinite > loop". I am getting out of memory because of this. > Can you please help me to resolve this. > > > > -- > View this message in context: > http://drools.46999.n3.nabble.com/Guvnor-test-scenario-executes-100000-times-tp4025816.html > Sent from the Drools: User forum mailing list archive at Nabble.com. > _______________________________________________ > rules-users mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-users _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
