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-... Sent from the Drools - User mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

I have been doing some more testing and have observed that the test case will actually sometimes evaluate to true. Out of 10 runs, 2 succeeded and 8 failed.

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-... Sent from the Drools - User mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users