]
Eli Israel commented on DROOLS-1364:
------------------------------------
I notice that the comment in the InMemorySessionFactory class reads:
// TODO all sessions stored here should be proxied so it can be removed on
dispose/destroy
Which would certainly cover the issue I noticed.
InMemorySessionFactory has apparent memory leak
-----------------------------------------------
Key: DROOLS-1364
URL:
https://issues.jboss.org/browse/DROOLS-1364
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 6.5.0.Final
Reporter: Eli Israel
Assignee: Mario Fusco
I'm running drools with a runtime manager creating using PerRequest strategy and
SessionCache turned on. (I process a LOT of requests but I want each one to be isolated)
The SessionCache properly gets rid of sessions that have hung around too long, which is
great.
But the InMemorySessionFactory keeps a copy of every session it ever created, which -- it
seems to me -- impedes garbage collection of unneeded, old sessions.
It's possible I'm just reading this wrong, but examinations of running code using
VisualVM show a LOT of RightTuple objects hanging around, attached to sessions and their
GC root appears to be the InMemorySessionFactory.