Details
Major Description
Currently the way rethrowException works it throws an exception with the stack where the ForeignException was locally created (normally where it gets deserialized, and with a getCause with the stack of the original thread on the remote thread.
Unfortunately, this doesn't provide any in formation about which call to rethrowException locally tripped over the exception. This simple patch wraps again to get the stack info which provides this missing context.