The original thread was for a bug in 5.0.x, fixed in 5.1, but it would be a
very serious issue in 5.5. It basically means that the local memory of a
beta node has been assigned to an alpha node, or that the wrong memory had
been retrieved. In any case, the rete is broken: wrong facts or types would
be joined in a different order or way than stated by the rules.
Is this something you're experiencing , or just worried that it may happen?
Causes could be an invalid rule in the first place (running the engine
without checking for compilation errors), a bug in the construction process
(unlikely, unless the rule is a very rare edge case), or a complex scenario
where you add and remove rules dynamically from a knowledge base.
On May 1, 2013 2:25 PM, "dcrissman" <dcrissman(a)redhat.com> wrote:
Could you explain what you mean by rete corruption? I am familiar
with
rete,
but hardly an expert. I am not really doing anything too complicated, I
guess some runtime inserts and retracts.
I tried 6.0.0.Beta2, but that has more api changes then I am prepared to
handle, I'll wait until the Final version.
As for 5.6.0-SNAPSHOT, I am having trouble pulling it down. I will pick
that
up tomorrow.
In the meantime, any clarification to the rete question would be
appreciated.
Thanks,
Dennis
--
View this message in context:
http://drools.46999.n3.nabble.com/java-lang-ClassCastException-org-drools...
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