anonymous wrote : In the case of servlet invoker, org.jboss.remoting.transport.http.WebServerError is thrown (or returned for the second invocation), so the original exception thrown on the server side is not the one thrown on the client side. Yes, that was my problem - my code relies on exceptions for creating user-friendly error messages. For now, I just modified servlet transport to preserve exception type. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003449#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...