[jboss-jira] [JBoss JIRA] (DROOLS-1199) Memory leak in KieScanner

[Joni Niemi (JIRA)]

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

Joni Niemi commented on DROOLS-1199:
------------------------------------

This bug makes version 6.4.0.Final unusable in a production environment. Your options are either to downgrade or fork and make your own build.

> Memory leak in KieScanner
> -------------------------
>
>                 Key: DROOLS-1199
>                 URL: https://issues.jboss.org/browse/DROOLS-1199
>             Project: Drools
>          Issue Type: Bug
>          Components: core engine
>    Affects Versions: 6.4.0.Final
>            Reporter: Viacheslav Krot
>            Assignee: Mario Fusco
>             Fix For: 7.0.0.Beta1
>
>
> I'm not sure, but it seems there is a memory leak in KieScanner, not in scanner directly, but somewhere in plexus used internally.
> If you start KieScanner with version = LATEST, start it with interval say 1 second and sample memory with visualvm (or any other), you can watch number of instances org.eclipse.sisu.plexus.* growing over time. And they cannot be garbage collected - memory root is timer thread. This happens in drools 6.4.0, in 6.3.0 this issue was absent.
> Eventually application fails with OOM.
> As a workaround we call KieScanner#scan manually in a separate thread pool that is recreated from time to time.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)