[
https://issues.jboss.org/browse/DROOLS-1364?page=com.atlassian.jira.plugi...
]
Eli Israel commented on DROOLS-1364:
------------------------------------
So, a quick correction: the SessionCache actually does NOT police its size, which means
that fast-moving code can absolutely fill the cache up with many, many unused sessions,
wreaking havoc on garbage collection as well.
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.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)