8:43 a.m.
Mario Fusco created JBRULES-3567:
------------------------------------
Summary: 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
--
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
8:45 a.m.
[
https://issues.jboss.org/browse/JBRULES-3567?page=com.atlassian.jira.plug...
]
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
11:29 a.m.
[
https://issues.jboss.org/browse/JBRULES-3567?page=com.atlassian.jira.plug...
]
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/16ab53ece99f75ab2b7759acdde07...
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
5056
days inactive
5056
days old
2 comments
1 participants
participants (1)
-
Mario Fusco (JIRA)