Having to deploy scoped is a known PITA, and can be very fiddly in certain situations. Also the "fat" jboss-messaging-client.jar introduces other issues with versions of dependencies. Our #1 source of support cases is "I am having classloader issues with messaging". These are almost always resolvable with some fiddling, but admittedly quite fiddly to get right. Do you have a support contract? If so, someone in support should be able to take you through getting it to work for your case. We are currently working hard to eliminate scoping and the "fat" client jar. This will be done in the 1.2.0.SP2 release, which is due in probably 2 or 3 weeks time. Once that release is out these kinds of problems should be a thing of the past. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040988#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...