[jboss-jira] [JBoss JIRA] Commented: (JBRULES-2313) Tomcat memery leak with drools 4.0.7 or 5.0.1

[Mark Proctor (JIRA)]

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

Mark Proctor commented on JBRULES-2313:
---------------------------------------

Are you sure the issue is not with Tomcat, which has a history of memory leaks on  classloaders and code generation.

Does the leak happen when executing on a pure JVM outside of tomcat?

> Tomcat memery leak with drools 4.0.7  or 5.0.1
> ----------------------------------------------
>
>                 Key: JBRULES-2313
>                 URL: https://issues.jboss.org/browse/JBRULES-2313
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-core  (expert)
>    Affects Versions: 4.0.7, 5.0.1.FINAL
>         Environment: XP tomcat 5.5.9
>            Reporter: GREFFET Emmanuel
>            Assignee: Mark Proctor
>            Priority: Critical
>              Labels: memory_leak, tomcat
>         Attachments: AnalyseDrools4&5MemoryLeak.doc, screenshot-1.jpg, tests.zip
>
>   Original Estimate: 3 weeks
>  Remaining Estimate: 3 weeks
>
> The memory is never released !!! (never ever )  when à Stop and Start or restart Tomcat.
> A made this test with a simple Drools call with a simple webapp and i tried with 4.0.7 and 5.0.1 drools version. The problem is the same.
> We need to stop tomcat process to release memory. Until this stop each Tomcat "Restart" with a drools call, will never release the memory.
> I made graphic with VisualWM, and we can see this problem !
> I made a zip of my simple Eclipse project (webapp + drools) and word file for more information and screen copy of VisualVM.
> Thanks for help.
> Emmanuel GREFFET ( FRANCE)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira