Hi, Brian! This one is a strange error... maybe the same class is being generated and loaded more than once by the same class loader? It's been a long time since I looked at the inner workings of unified class loaders and redeploy. If there is this possibility, let's first rule this one out. Can you make this error happen twice in a row? I mean, if you run the the test three times, at the first time it will probably run ok, at the second one it will fail, and at the third one? If this one also fails, I can see if the name of the problematic generated class is the same in both error instances. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4061448#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...