[jboss-jira] [JBoss JIRA] (DROOLS-647) memory leak

Mario Fusco (JIRA) issues at jboss.org
Tue Nov 18 09:04:39 EST 2014


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

Mario Fusco commented on DROOLS-647:
------------------------------------

Yes, the fix is present on the 6.2.x branch. 
We are not planning to deploy a patch release of the 6.1.x so you'll have to use the 6.2.0 release to have this fix.
You can already give a try to the 6.2.0.CR2 and check if this fixes your problem. The final release will be available in a few weeks.

Mario

> memory leak
> -----------
>
>                 Key: DROOLS-647
>                 URL: https://issues.jboss.org/browse/DROOLS-647
>             Project: Drools
>          Issue Type: Bug
>    Affects Versions: 6.1.0.Final
>            Reporter: Dawna Floyd
>            Assignee: Mario Fusco
>             Fix For: 6.2.0.CR3
>
>         Attachments: DROOL_TEST.zip
>
>
> references to fact handles not being removed when objects are removed from memory. Converted  our application from 5.0.1 to 6.1_Final and encountered memory leaks in the drools processing. Found references to defect 498 and checked out the 6.1.1 code based and built the source (the download package doesn't seem to have these fixes). The majority of leaks were corrected with this code line, however there still remains a memory leak when we run our defined rules. Even though a rule never fires,  it's evaluation seems to hold onto beta memory forever and the test application will eventually run out of memory.  I can provide a test program that highlights the leak.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)


More information about the jboss-jira mailing list