we are seeing similar memory leak with 5.2.0.Cr1 version of drools.
are there any other alternatives such as using a different version of jbpm
jar if that is the cause of the problem?
we are currently using the jbpm-flow-5.1.0.Cr1.jar.
If not,
is there a method that removes all the facts from the ksession so that it
can be reused?
for ex, the existing code (simplified) is as follows:
ksession = knowledgeBase.newStatefulKnowledgeSession();
for (Object obj : objList)
{
ksession.insert(obj);
}
ksession.startProcess(ruleFlowProcessName);
ksession.fireAllRules();
.... do some response processing here
ksession.dispose();
Thomas,
Can you please elaborate on what you did to clean out the facts from the
memory ?
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Memory-leak-in-5-2-5-3-tp32...
Sent from the Drools: User forum mailing list archive at
Nabble.com.