If I have problem on the Java-side implementation, the default error
handler only shows the topmost Java exception. What is the best way to
get the information from nested causes?
Or to explain this in computer words: Exceptions with deep causes. JRuby only shows the latest level, i.e. 'Exception on level 8' without any insight into the deeper causes. · GitHub