such problems are solved using class loading information through JMX console: http://172.16.100.70:8080/jmx-console/HtmlAdaptor choose under JMImplementation to click on LoaderRepository: JMImplementation * name=Default,service=LoaderRepository then go to displayClassInfo and enter all class path: java.lang.String displayClassInfo() MBean Operation. Param ParamType ParamValue ParamDescription p1 java.lang.String (no description) that way you have the information on the location of the class. That way I could notice it was using a jar in another location than I thought. Catherine View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4103963#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...