[rules-users] Different rule fires when debugging vs running after upgrading to 5.1.1

[Greg Barton]

You've already pointed to it yourself.  Rules execution should be thought of in the same way you approach concurrent programming.  Execution can (and should) be able to happen in any order possible.  Only the current logical state of working memory should influence the next step in execution, with a bit of arbitrary choice thrown in. (The last step in conflict resolution between rules is "pick one...")

GreG

On Jan 19, 2011, at 14:16, "H.C." <canterburry at gmail.com> wrote:

> 
> I certainly do appreciate the help and fully understand no one here will be
> able to give me a concrete solution without a test case. I was just hoping
> that describing the behavior would jog something in someone's head which
> would lead to a pointed question that may help steer me in the right
> direction of searching for the cause.
> -- 
> View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Different-rule-fires-when-debugging-vs-running-after-upgrading-to-5-1-1-tp2283993p2290099.html
> Sent from the Drools - User mailing list archive at Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users