Ah, I see. In ClassLoaderManager:201, the task list is never empty in the unit test, so
it never waits, and thus never triggers the error.
No idea how to trick it into waiting though.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215055#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...