I forgot to note that I am using 5.1.M1.
-Heath
--
View this message in context:
http://n3.nabble.com/marshal-ActionNodeInstance-tp467573p467576.html
Sent from the Drools - User mailing list archive at Nabble.com.
___
rules-users mailing list
rules-us
Hello List,
I am marshalling using the DefaultMarshaller in drools and get the following
error:
java.lang.IllegalArgumentException: Unknown node instance type:
org.drools.workflow.instance.node.actionnodeinsta...@d20c43
at
org.drools.marshalling.impl.AbstractProcessInstanceMarshaller.writeNodeIn
I think I need to clarify a few things. First the OOME is not in running the
rules but on marshalling the state for the flow, which I do after each
command using a custom CommandService that marshals the session after each
command is executed. Second, the ValidationRuleFlowGroup is only going to
i
I am using drools marshalling for persistence and am getting an OOME with my
simple rule flow. I have a custom CommandService that persists at the end of
each execution. (I am not using JPA :-( ).
In the rule flow I have a split that checks for the non-existence of a
simple pojo using "not Valida
I was able to resolve this problem. What it came down to was a deadlock
trying to get a global, a Log4J logger, while another thread fire until halt
had control of the lock in AbstractWorkingMemory.
-Heath
--
View this message in context:
http://n3.nabble.com/StatefulKnowledgeSession-synchroniz
I don't think this isn't fixed in trunk.
I grabbed the latest drools 5.1.0 SNAPSHOT from
https://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/trunk/target/drools-5.1.0.SNAPSHOT-bin.zip,
and now I get the same stack trace for the blocked thread with different
line numbers.
org.
Hello,
Using Drools 5.1.0.M1.
I am running into a blocking problem when I concurrently try to update a
fact in my knowledge session, which is fireUntilHalt() in its own thread,
from another thread, an updator thread. I know that only these 2 threads are
ever accessing each knowledge session.
Ha
