Major Description
Currently, the exceptions thrown by the Java client tend to have stack traces showing the point at which some error callback is called. The stack usually leads back to Netty reading a response from the wire, and not from the actual user code which invoked the call.
For the async client this is somewhat unavoidable, and I think people have gotten used to stack traces in async clients being rather useless. But, in the synchronous wrapper, we should rewrite the stack traces so that the user's actual call stack is preserved.