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

[H.C.]

I just upgraded Drools from 5.0.1 to 5.1.1 and am facing failures in our
Junit tests after the upgrade (test worked in 5.0.1). 

I have two rules that are mutually exclusive on the value of a particular
attribute. When debugging, this attribute has the expected value and the
first rule fires. When running, a the audit shows the other rule firing thus
the attribute must be null at runtime.

Any reason why a different set of rules may have fired during debugging vs
running?

Thanks
-- 
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-tp2283993p2283993.html
Sent from the Drools - User mailing list archive at Nabble.com.