I can't say in general, it would depend on the expression.
I suspect this is a case where you have something like.
a == x || b == y
At some point MVEL "kicks in" and tries to optimize the expression,
but will fail if b ==y has never been evaluated because a == x
has always been satisfied by your current data.
In any case, I doubt the gain would be noticeable.
I think there was a similar discussion in one of the threads some week ago,
but I'm not sure whether it was here or on IRC :)
Davide

On 05/04/2013 09:36 AM, Sean Su wrote:
Thanks Davide. Does this mean there might be a better way to write the expression that triggered this? If yes, I will look into it. I think the log does have the statement in it.

Sean


On Sat, May 4, 2013 at 3:13 AM, Davide Sottara <dsotty@gmail.com> wrote:
That exception is the result of an unsuccessful attempt to optimize some
constraint execution.
That optimization is optional - exactly because it's not guaranteed to
succeed - so the engine
can continue normally. The exception is logged for tracing purposes
Best
Davide



--
View this message in context: http://drools.46999.n3.nabble.com/rules-users-Drools-5-5-run-time-exception-from-the-library-code-but-no-impact-to-the-rule-evaluationt-tp4023669p4023678.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users



_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users