[
https://issues.jboss.org/browse/AS7-1098?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on AS7-1098:
-------------------------------------
bind does
clBindings.put(Thread.currentThread().getContextClassLoader(), dirContext)
unbind does
clBindings.put(Thread.currentThread().getContextClassLoader())
Before bind is called the TCCL is set to the deployment class loader, however before
unbind is called the old tccl is restored (unbind should be called before the TCCL is
restored).
This means that when bind is called the TCCL is the deployment class loader, but when
unbind is called the class loader is the restored class loader, which is usually null.
org.apache.naming.resources.DirContextURLStreamHandler holds onto
ClassLoader after deployments have been undeployed
--------------------------------------------------------------------------------------------------------------------
Key: AS7-1098
URL:
https://issues.jboss.org/browse/AS7-1098
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.0.0.Beta3
Reporter: Stuart Douglas
Fix For: 7.0.0.CR1
DirContextURLStreamHandler.clBindings is holding onto class loaders of previos
deployments. This can be observed by running the integration tests and then examining the
class loaders in the map in a debugger.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira