I didn't mean ignore it, just defer it - after all the thread could be asynchronously interrupted and I don't think that the best thing to do would be to blow up in that case. Anyway, consuming the InterruptedException is definitely the wrong thing to do regarless of where the status is being set (and that's really what it's doing now, looking at ClassLoaderManager.java:169). It should catch the exception, set a flag, continue what it's doing, then reset the interrupt status on exit; that or rethrow InterruptedException (which it cannot do in this case, since loadClass doesn't throw that exception). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214959#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...