There are two answers:<br>a) factor X<br>b) not the same code or data or both<br><br>Some code to reproduce this might lead to a definite answer.<br>-W<br><br><div class="gmail_quote">On 19 January 2011 00:41, H.C. <span dir="ltr">&lt;<a href="mailto:canterburry@gmail.com">canterburry@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
I just upgraded Drools from 5.0.1 to 5.1.1 and am facing failures in our<br>
Junit tests after the upgrade (test worked in 5.0.1).<br>
<br>
I have two rules that are mutually exclusive on the value of a particular<br>
attribute. When debugging, this attribute has the expected value and the<br>
first rule fires. When running, a the audit shows the other rule firing thus<br>
the attribute must be null at runtime.<br>
<br>
Any reason why a different set of rules may have fired during debugging vs<br>
running?<br>
<br>
Thanks<br>
<font color="#888888">--<br>
View this message in context: <a href="http://drools-java-rules-engine.46999.n3.nabble.com/Different-rule-fires-when-debugging-vs-running-after-upgrading-to-5-1-1-tp2283993p2283993.html" target="_blank">http://drools-java-rules-engine.46999.n3.nabble.com/Different-rule-fires-when-debugging-vs-running-after-upgrading-to-5-1-1-tp2283993p2283993.html</a><br>

Sent from the Drools - User mailing list archive at Nabble.com.<br>
_______________________________________________<br>
rules-users mailing list<br>
<a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
</font></blockquote></div><br>