With the fix for 4010355 ("exceptions thrown by remote methods should retain
server's stack trace") integrated, RMI now serializes and retains the
server-side stack traces of server exceptions. There are, however, instances
where this behavior may not be desirable:

  - RMI-exported remote objects may not wish to reveal the server-side stack
    trace for security reasons.

  - RMI-exported remote objects may wish to avoid the performance hit of
    initializing and sending server-side stack trace information (benchmarking
    has shown the cost of initializing/sending stack traces to be significant).

For these reasons, there should be a means of configuring RMI (perhaps a global
system property) so that it will not initialize and send exception stack
traces. Stack trace initialization/transmission could be avoided by calling
setStackTrace() with a zero-length array on the server-side before marshalling
the exception.