[
https://jira.jboss.org/browse/JBAS-8424?page=com.atlassian.jira.plugin.sy...
]
David Allen commented on JBAS-8424:
-----------------------------------
As far as I can see, the FilterDispatcher will indirectly setup a new
ResteasyProviderFactory for the application. This eventually is added to a
ThreadLocalResteasyProviderFactory which keeps a static reference to thread locals
(indirect). Later when an app is undeployed, the filter's destroy() method is called,
but there is no code in this filter method. So it appears that no code is ever executed
to remove the ResteasyProviderFactory from the thread local variable.
Since it is a static ref, and the ThreadLocalResteasyProviderFactory is still loaded by a
CL, it's references are never freed. The BeanManager is leaked through the
CdiInjectorFactory used by the ResteasyProviderFactory for Weld applications.
RestEasy deployer won't release Weld BeanManager on undeploy
------------------------------------------------------------
Key: JBAS-8424
URL:
https://jira.jboss.org/browse/JBAS-8424
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: 6.0.0.CR1
Environment: JBoss AS 6.0.0-SNAPSHOT, Linux 64 bit
Reporter: David Allen
Assignee: Bill Burke
Priority: Blocker
ThreadLocalResteasyProviderFactory in RestEasy has a reference to a CdiInjectorFactory
that is not released when the application is undeployed from JBoss AS. This
CdiInjectorFactory holds a reference to a BeanManager from Weld, and thus leaks all the
beans from the deployment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira