Exception stacktrace truncated

Question

Hello, all.
Is there a way to stop this exception stacktrace trunctation "feature" that seems to come with 1.4.x ? Here's an example:
Caused by: java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at javax.media.jai.FactoryCache.invoke(FactoryCache.java:130)
     at javax.media.jai.OperationRegistry.invokeFactory(OperationRegistry.java:1682)
     ... 14 more
Caused by: javax.media.jai.util.ImagingException: All factories fail for the operation "encode"
     at javax.media.jai.OperationRegistry.invokeFactory(OperationRegistry.java:1695)
     at javax.media.jai.ThreadSafeOperationRegistry.invokeFactory(ThreadSafeOperationRegistry.java:481)
     at javax.media.jai.registry.RIFRegistry.create(RIFRegistry.java:340)
     at com.sun.media.jai.opimage.FileStoreRIF.create(FileStoreRIF.java:143)
     ... 20 more
The ...14 more, and ...20 are getting on my nerves. There's no point in knowing how deep the stack trace is If I don't know where it begins. I wonder who in the Java team came up with this bright idea.
Anyways, does anyone know how to get rid of this and have the complete stack trace displayed.
Thanks,
Sonny

Answer 1

One think to note is that even though it truncates some of the exceptions, you aren't actually losing any information. Its all in how you read it.
For example, this test program: package teststacktrace;
public class TestStackTrace {
    public static void main(String[] args) {
        try {
            method1();
        } catch (java.sql.SQLException e) {
            throw new RuntimeException("RuntimeException", e);
    private static void method1() throws java.sql.SQLException {
        try {
            method2();
        } catch (java.io.IOException e) {
            throw (java.sql.SQLException) new java.sql.SQLException("SQLException").initCause(e);
    private static void method2() throws java.io.IOException {
        throw new java.io.IOException("IOException");
}produces this stacktrace:
java.lang.RuntimeException: RuntimeException
     at teststacktrace.TestStackTrace.main(TestStackTrace.java:10)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.intellij.rt.execution.application.AppMain.main(AppMain.java:78)
Caused by: java.sql.SQLException: SQLException
     at teststacktrace.TestStackTrace.method1(TestStackTrace.java:18)
     at teststacktrace.TestStackTrace.main(TestStackTrace.java:8)
     ... 5 more
Caused by: java.io.IOException: IOException
     at teststacktrace.TestStackTrace.method2(TestStackTrace.java:23)
     at teststacktrace.TestStackTrace.method1(TestStackTrace.java:16)
     ... 6 moreYou'll notice that the last method mentioned in a deeper exception (textually lower in the list) overlaps with the first method mentioned in the next exception. Everything that follows the overlapping line is essentially what was truncated from the lower exception.
So to read the full depth, you read the stack trace of the top exception from bottom to top, then read the stack trace of the next exception from bottom to top etc.
T