1

I'm missing a stack trace in my log file and I believe it is due to the stack trace being optimized away be the JVM (see NullPointerException in Java with no StackTrace)

I have tried to pass in -XX:-OmitStackTraceInFastThrow via my jnlp file like this: 

...java-vm-args="-XX:-OmitStackTraceInFastThrow"...

but it has no effect. And it looks like setting -XX:-OmitStackTraceInFastThrow (see JNLP File Syntax) via java-vm-args is not supported.

Is there another way of stopping the JVM from omitting stack traces?

--- Edit:

I added -XX:-OmitStackTraceInFastThrow via

Control Panel > Java > Java (tab) > View (button) > Runtime parameters (field)

as (described here) that worked fine.

Community
  • 1
  • 1
cmadsen
  • 354
  • 4
  • 19
  • I don't remember if this is an option that can be changed while the VM is running but it may be worth a try. – biziclop Jul 14 '15 at 12:22
  • No, `OmitStackTraceInFastThrow` cannot be changed in run-time. Try setting `-client` or `-Xint` JVM argument to disable server compiler. The application will run slower, but it won't skip stacktraces. – apangin Jul 14 '15 at 18:00

0 Answers0