Thanks Mark.
Regarding the scenario you're mentioned: "If some how a LeftTuple is created
by one node, but used by a different node"
What could be reasons causing the logic running into this? Will it be
something with multi-threaded environment or incremental change-set update?
--
View this me
Hi,
After upgrading from 5.0.1 to 5.4.0, i've experienced some unresolvable
issue
(http://drools.46999.n3.nabble.com/UnsupportedOperationException-intermitently-tp4022719.html).
As reproducing the issue is totally not trivial and i can't prove if
upgrading to 5.5 or even 5.6 would warantee fixi
I can't post exact rule sheet here and only anonymized and simplified version
of it
package com.mycompany;
import com.mycompany.model.TAD;
import com.mycompany.model.IED;
rule "r_19"
no-loop true
salience 1999
activation-group "Update1"
when
tad:TAD
Reformat my mail so it's readable ...
We've upgraded Drools 5.1 to 5.4.0.Final. Everything is great with new
incremental build change-set.
However, occasionally we get this error (so far, 2 different stack trace)
java.lang.UnsupportedOperationException
at org.drools.reteoo.BaseLeft
We've upgraded Drools 5.1 to 5.4.0.Final. Everything is great with new
incremental build change-set.However, occasionally we get this error (so
far, 2 different stack trace)java.lang.UnsupportedOperationException
at org.drools.reteoo.BaseLeftTuple.getObject(BaseLeftTuple.java:589)
at
Appreciate for the useful info, Mark.
--
View this message in context:
http://drools.46999.n3.nabble.com/Loading-rules-performance-problem-in-5-4-0-Beta2-compare-to-5-0-1-tp3768609p3777289.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
__
Hi all,
I'm planning to upgrade to Drools 5.4.0.Beta2 from 5.0.1.
However when testing the performance w.r.t rules loading, 5.4.0.Beta2 is not
only much slower (50% slower) but also eats more memory compare to 5.0.1.
Is it something expected from 5.4.0.Beta2 to compensate other
fixes/features?
