No, there isn't any option to change the exception chain propagation. In fact, our trend
has been to increase the amount of information that is chained so that the developer is
not forced to have to always look in the server.log for the source of the problem and
to increase the chance that the root cause is made known.
However, as you point out, the behavior you're seeing is a bug. The client application
shouldn't be receiving an arbitrary runtime exception. Could you please file an bugster issue
for this and include all the stack traces. Thanks.
[Message sent by forum member 'ksak' (ksak)]
http://forums.java.net/jive/thread.jspa?messageID=222008