[jboss-jira] [JBoss JIRA] Created: (JBRULES-2266) Memory leaks where the classloader cannot be garbage collected / impossible to dispose tomcat devloader when i reload context (drools keep reference)...

[GREFFET Emmanuel (JIRA)]

Memory leaks where the classloader cannot be garbage collected / impossible to dispose tomcat devloader when i reload context (drools keep reference)...
--------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: JBRULES-2266
                 URL: https://jira.jboss.org/jira/browse/JBRULES-2266
             Project: Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: All
    Affects Versions: 4.0.7
         Environment: XP SP2    2Mo     Tomcat 5.5.9 /  drools 4.0.7 

            Reporter: GREFFET Emmanuel
            Assignee: Mark Proctor
            Priority: Critical


(sorry for my English) We use drools 4.0.7 
in a hospital application.
 We load drools and our programs (services) with tomcat Devloader 
 (5.5.9) We use drools in statefullsession (retract and insert facts 
 by rules in a ruleFlow).
 everything is perfect for us, except a little problem of "dispose" 
 with tomcat due to drools.
 Through the Tomcat console when we try to restart our webapp, tomcat 
 can't dispose the old Devloader (in Eclipse we can see that many 
 drools class use class attribute ClassLoader without any dispose ???) 
 In production, we used different webapps in a Tomcat, so we can't 
easily stop Tomcat, so until we stop tomcat, the reload of the 
 webapps is longer and longer ... (many devloader(s) can't dispose)...
anyone has had this problem ?


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira