[jboss-jira] [JBoss JIRA] (JBRULES-3567) Too many class loaders created during jitting by the ClassGenerator

Mario Fusco (JIRA) jira-events at lists.jboss.org
Tue Jul 3 12:29:12 EDT 2012


     [ https://issues.jboss.org/browse/JBRULES-3567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mario Fusco resolved JBRULES-3567.
----------------------------------

    Fix Version/s: 5.4.1.Final
                   5.5.0.Beta1
       Resolution: Done


fixed by https://github.com/droolsjbpm/drools/commit/16ab53ece99f75ab2b7759acdde076f8b9ce3cf8
                
> Too many class loaders created during jitting by the ClassGenerator
> -------------------------------------------------------------------
>
>                 Key: JBRULES-3567
>                 URL: https://issues.jboss.org/browse/JBRULES-3567
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Mario Fusco
>            Assignee: Mario Fusco
>             Fix For: 5.4.1.Final, 5.5.0.Beta1
>
>
> The current implementation of the ClassGenerator causes the following classloading leaks:
>   
>   * org.drools.rule.builder.dialect.asm.ClassGenerator.EMPTY_METHOD_BODY is a static instance which will hold to the last instance of InternalClassLoader created
>   * org.drools.rule.constraint.MvelConstraint uses an ExecutorHolder that spawns daemon threads and keeps them in a pool. Problem is these threads create class loaders, and can only be garbage collected when the thread dies

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list