Hi,
We are having the same problem with a similar setup (drools 5.2.0 Final)
using stateless sessions and camel integration, using a KB with ~3000 rules.
Session memory is never reclaimed, and after some hours we got an out of
memory error. We still dont know the cause, but the profiler shows that
these objects are increasing rapidly:
org.drools.reteoo.BetaMemory 176.478
+176.163 (+55925 %) 6.893 kB
org.drools.core.util.LeftTupleList 175.467
+175.156 (+56320 %) 6.854 kB
org.drools.core.util.RightTupleList 172.806
+172.536 (+63902 %) 6.750 kB
org.drools.rule.ContextEntry[ ] 164.784
+164.724 (+274540 %) 2.659 kB
org.drools.core.util.Entry[ ]
160.520 +160.449 (+225985 %) 16.561 kB
org.drools.core.util.ObjectHashMap 158.309 +158.253
(+282595 %) 6.183 kB
org.drools.reteoo.AccumulateNode$AccumulateMemory 154.505 +154.503
(+7725150 %) 4.828 kB
org.mvel2.integration.impl.IndexVariableResolver 76.262 +76.234
(+272264 %) 1.787 kB
We used drools 5.1.1 before with no problems, so we think this leak is
upgrade related.
Regards,
TL
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Drools-Execution-Server-mem...
Sent from the Drools: User forum mailing list archive at
Nabble.com.