Ron - I went by memory in my initial reply, so I got a couple details wrong - sorry, it was the weekend :-). (Birthday weekend, no less!) That said, you're right about the processRequest method that's called. The source code that gets executed for us is the following: try | { | // call transport on the subclass, get the result to handback | invocationResponse = invoke(invocationRequest); | } | catch(Throwable ex) | { | log.debug("Error thrown calling invoke on server invoker.", ex); | invocationResponse = ex; | isError = true; | } | I downloaded the source code for 2.2.2.SP1 and see what you posted, with the checkForExceptionReturn(metadata) method call. When I attach the debugger to that source, however, the checkForExceptionReturn method is never invoked - isError is set immediately. Attaching the debugger with code from JBossRemoting-2_2_0_GA partially lines up (at least in behavior if not exact line numbers while debugging). See [1] for a screenshot that includes the return-exception set to true (in the variables debug window). Even though it's true, it never gets returned. The moral of the story: we seem to have an outdated version of JBoss both on our development machines (4.2.2 GA) and in production (JBoss-AS 4.3 sans patches). Given the code you showed us, it should indeed fix the issue. Regarding the WebServerError, "NoThrowOnError" isn't set anywhere that I can see. I think before we spend any more of anybody's time, we should upgrade all our servers to the latest patch of JBoss-AS 4.3. I just downloaded jboss-eap-4.3.0.GA_CP03.zip via the link provided in the service ticket. I poked around a bit looking for the source, but couldn't find it -- is it available, and if so, could you send a link? Thanks for your help Ron. Dave [1] - http://www.seinberg.net/images/stack.png View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189835#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...