Print out full error message from java via commandline

Question

I'm currently running an application that can only be run through a program/s commandline which uses java. When I get my error print out, how do I view the full print out?

i.e. how do i see the "13 more"

Exception:
        java.lang.reflect.InvocationTargetException
        (rethrown as com.comsol.util.exceptions.FlException)
Messages:
        Error running java class
        - Detail: Error_running_java_class

Stack trace:
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at com.comsol.util.application.CsBaseApplication.runExternalClassStat(Unknown Source)
        at com.comsol.util.application.CsBaseApplication.runExternalClass(Unknown Source)
        at com.comsol.util.compile.a$a.a(Unknown Source)
        at com.comsol.util.compile.a$a.call(Unknown Source)
        at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.IndexOutOfBoundsException: Index: 4, Size: 4
        at java.util.ArrayList.RangeCheck(Unknown Source)
        at java.util.ArrayList.get(Unknown Source)
        at Enviornment.makeNextGen(Enviornment.java:269)
        at Enviornment.main(Enviornment.java:44)

        ... 13 more

If you can't output to a file, isn't this more of an OS problem rather than a Java problem? — Hovercraft Full Of Eels, Jul 24 '11 at 01:33
see http://stackoverflow.com/questions/1043378/print-full-call-stack-on-printstacktrace/1043484#1043484 — akf, Jul 24 '11 at 01:38

Alex Gitelman · Accepted Answer · 2011-07-24T01:50:25.190

This stack trace contains everything you need to know and is not related to console output. It just skips repeating lines.

Update.

Suppose your method call a() calls b() and b() catches exception thrown from some other method foobar(), wraps it in another exception and rethrows it. Here is how stack traces will look:

void b() {
   try {
     foobar();
   } catch(Exception e) {
     // Stack trace for e:
     // foobar()
     // b()
     // a()
     throw new RuntimeException("error",e); 
  }
}

void a() {
  try {
    b(); 
  } catch(Exception e) {
   // Stack trace for e
   // b()
   // a() 
   // Cause:
   // foobar()
   // b() - repeating line
   // a() - repeating line
   e.printStackTrace();
  } 
}

So code that prints exception just skips repeating lines as they carry no additional value. In your question there is InvocationTargetException being thrown in place of RuntimeException in my example. InvocationTargetException is exception typically used by reflection.

This is underlying exception that was thrown in reflection call. It's returned as `cause` in `InvocationTargetException` — Alex Gitelman, Jul 24 '11 at 01:36
So the "13 more" would simply be repeats of what was already printed before? — randomafk, Jul 24 '11 at 01:45

score 1 · Answer 2 · answered Jul 24 '11 at 01:55

See http://www.docjar.com/html/api/java/lang/Throwable.java.html#671 for the code that generates the 13 more in your case.

It counts the stack trace elements that this exception has in common with the previously printed exception. So you know that you have to add the last 13 lines (which in this case means all) from the exception above to the truncated trace.

Print out full error message from java via commandline

2 Answers2

Linked