Remoting wraps server-side exceptions and propagates them on the client. I found this quite useful while debugging. Actually they use a neat trick that makes the exception stack trace look continuous, so you can see the error propagation path very clearly. No matter how we do it, if something breaks on the server-side, the client stack trace should give a hint of what went wrong, not just "JMSEXception: something is wrong on the server". The problem with a) can be solved by simply including the exception classes into the client jar. Why is this difficult? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959732#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...