[jboss-jira] [JBoss JIRA] (DROOLS-1364) InMemorySessionFactory has apparent memory leak

[Eli Israel (JIRA)]

    [ https://issues.jboss.org/browse/DROOLS-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13326658#comment-13326658 ] 

Eli Israel commented on DROOLS-1364:
------------------------------------

Thanks, Maciej.

The reason I use the runtime manager is that I have additional rule packages that I want to add and remove on the fly. (Our product presents the user with the ability to specify if-this-then-that style actions based on Twitter events).

Couldn't see a way to do that without managing a KFS/KieContainer. Then when I wanted to switch to PerRequest, it seemed to me that you have to configure and use the runtime managers. Tell me if I have that wrong.



> 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: Maciej Swiderski
>
> 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)