10:15 a.m.
Just want to put the exception out here in case it is meaningful to the
development or whoever ran into this before. It occurred but does not
impact the result of the process.
Exception in thread "Thread-6" java.lang.NullPointerException
at java.lang.String.<init>(String.java:210)
at org.mvel2.ast.ASTNode.toString(ASTNode.java:426)
at org.mvel2.ast.Or.toString(Or.java:59)
at java.lang.String.valueOf(String.java:2826)
at java.lang.StringBuilder.append(StringBuilder.java:115)
at
org.drools.rule.constraint.ConditionAnalyzer.analyzeNode(ConditionAnalyzer.java:247)
at
org.drools.rule.constraint.ConditionAnalyzer.analyzeSingleCondition(ConditionAnalyzer.java:106)
at
org.drools.rule.constraint.ConditionAnalyzer.analyzeCondition(ConditionAnalyzer.java:99)
at
org.drools.rule.constraint.ConditionAnalyzer.analyzeCondition(ConditionAnalyzer.java:70)
at
org.drools.rule.constraint.MvelConditionEvaluator.getAnalyzedCondition(MvelConditionEvaluator.java:83)
at
org.drools.rule.constraint.MvelConstraint.executeJitting(MvelConstraint.java:270)
at
org.drools.rule.constraint.MvelConstraint.access$200(MvelConstraint.java:51)
at
org.drools.rule.constraint.MvelConstraint$ConditionJitter.run(MvelConstraint.java:250)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Sean
2:13 a.m.
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-excepti...
Sent from the Drools: User forum mailing list archive at Nabble.com.
11:36 a.m.
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(a)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-excepti...
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
12:28 p.m.
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(a)gmail.com
<mailto: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-excepti...
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org <mailto:rules-users@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
4254
days inactive
4255
days old
3 comments
2 participants
participants (2)
-
Davide Sottara -
Sean Su