Session.executor is leaking the first classLoader used
------------------------------------------------------
Key: JBMESSAGING-1200
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-1200
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP2
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
The Session.executor is holding the first ClassLoader reference on its
ThreadContextClassLoader.
This is also causing invalid classLoader usages when the first ClassLoader used was
undeployed, and could lead to other problems on ObjectMessages and StreamMessages. (things
like ClassNotFound becuase it's using the wrong classLoader on the executor).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira