No StackTrace in java.lang.NullPointerException

iteye_4021

于 2010-02-01 22:39:35 发布

阅读量185

点赞数

CC 4.0 BY-SA版权

分类专栏：默认类别文章标签： Java log4j J2SE performance SUN

本文链接：https://blog.youkuaiyun.com/iteye_4021/article/details/81822685

默认类别专栏收录该内容

2 篇文章

订阅专栏

本文介绍如何通过设置新的JVM标志-XX:-OmitStackTraceInFastThrow来完全禁用使用预分配异常，这些异常在多次抛出后为了性能而被编译器采用，但不提供堆栈跟踪。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

The compiler in the server VM now provides correct stack backtraces for all "cold" built-in exceptions. For performance purposes, when such an exception is thrown a few times, the method may be recompiled. After recompilation, the compiler may choose a faster tactic using preallocated exceptions that do not provide a stack trace. To disable completely the use of preallocated exceptions, use this new flag: -XX:-OmitStackTraceInFastThrow
[url]http://stackoverflow.com/questions/1142007/why-does-log4j-disable-stack-trace-after-lots-of-repetition-of-the-same-excepti[/url]
[url]http://java.sun.com/j2se/1.5.0/relnotes.html#hotspot[/url]