[
https://issues.jboss.org/browse/AS7-1098?page=com.atlassian.jira.plugin.s...
]
Remy Maucherat commented on AS7-1098:
-------------------------------------
"This appears to be because StandardContext.bindThread and
StandardContext.unbindThread are called with different context class loaders."
Hum, I don't think so, bindThread sets the TCCL to getLoader().getClassLoader(), and
unbindThread restores the TCCL that was there before. How is that wrong ?
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