The combination of a stateLESS session and this particular handling of the
RuleFlowGroupDeactivatedEvent looks strange to me. Consider that after
this code executes, all facts are gone, but a stateLESS session can't
be populated with fresh facts, since after the return from the
execute(.) call, the session itself is a goner, having been
dispose()-d automatically.
-W
On 26/02/2013, ismaximum <mnrz57(a)gmail.com> wrote:
Well, actually we are migrating from 4.x to 5.5, a big jump :)
So far we had a lot of issue with this migration and now this is occurring.
We had no issue with v4 and since we are still working on this migration I
can't say whether the system works properly or not because we need to fix
rules otherwise they don't work at all.
We are using Stateless sessions and we don't have any retracting policy.
This retracting policy you said, made me a bit concerned. Now the question
is where is the right place to do this? I put below code in the event
listener, is that the right place and right way to do it?
@Override
public void afterRuleFlowGroupDeactivated(
org.drools.event.rule.RuleFlowGroupDeactivatedEvent e) {
Collection<FactHandle> handlers =
e.getKnowledgeRuntime().getFactHandles();
if(handlers != null) {
for(FactHandle fh : handlers) {
e.getKnowledgeRuntime().retract(fh);
}
}
}
Thanks
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-GC-Overhead-Limit-Exceeded-...
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