Changing directions, this seems a bit more likely:
java.lang.Thread has a field "contextClassLoader". Remoting ServerThread
inherits this, and the ServerThread hangs around after invocations (until timeout).
So if the BaseClassLoader instance in there is the one we're leaking, that could be
it. Continuing to verify.
S,
ALR
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175696#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...