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

[Mario Fusco (JIRA)]

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

Mario Fusco updated JBRULES-3567:
---------------------------------

    Description: 
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

    
> 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
>
> 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