It seems to have been a classpath problem on the client side. I had jboss-messaging-client.jar in the client-side java.classpath *after* remoting, serialization, and trove. Changing its position fixed the problem. I'm basically ready to commit the changes to allow running generic test cases from testsuite/src/main/org/test/jbossmessaging, but i'll wait until Monday to do it, just incase there are any mistakes which need rectifying. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978298#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...