java – 哪个JVM打印出这样的线程转储?

前端之家收集整理的这篇文章主要介绍了java – 哪个JVM打印出这样的线程转储?前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。
我习惯于看到如下所示的 Java线程转储,这是由Sun HotSpot JVM及其衍生产品(如OpenJDK)生成的:
"main" prio=10 tid=0x00007f4020009000 nid=0x538c in Object.wait() [0x00007f402891f000]
   java.lang.Thread.State: WAITING (on object monitor)
    at java.lang.Object.wait(Native Method)
    - waiting on <0x0000000614ea64e8> (a java.lang.Object)
    at java.lang.Object.wait(Object.java:503)
    at org.eclipse.jetty.util.thread.QueuedThreadPool.join(QueuedThreadPool.java:386)
    - locked <0x0000000614ea64e8> (a java.lang.Object)
    at org.eclipse.jetty.server.Server.join(Server.java:398)
    at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:531)
    at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:364)
    at org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:528)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)

现在,在协助其他用户使用我的软件时,我偶尔会遇到另一种形式的线程转储,如下所示:

Thread 9255: (state = BLOCKED)
 - sun.reflect.annotation.AnnotationType.getInstance(java.lang.Class) @bci=0,line=63 (Interpreted frame)
 - sun.reflect.annotation.AnnotationParser.parseAnnotation(java.nio.ByteBuffer,sun.reflect.ConstantPool,java.lang.Class,boolean) @bci=94,line=202 (Interpreted frame)
 - sun.reflect.annotation.AnnotationParser.parseAnnotations2(byte[],java.lang.Class) @bci=39,line=69 (Compiled frame)
 - sun.reflect.annotation.AnnotationParser.parseAnnotations(byte[],java.lang.Class) @bci=11,line=52 (Compiled frame)
 - java.lang.Class.initAnnotationsIfNecessary() @bci=22,line=3070 (Interpreted frame)
 - java.lang.Class.getAnnotation(java.lang.Class) @bci=13,line=3029 (Interpreted frame)
 - com.google.inject.internal.Annotations.isRetainedAtRuntime(java.lang.Class) @bci=3,line=57 (Interpreted frame)
 - com.google.inject.Key.ensureRetainedAtRuntime(java.lang.Class) @bci=1,line=362 (Interpreted frame)
 - com.google.inject.Key.strategyFor(java.lang.annotation.Annotation) @bci=15,line=339 (Interpreted frame)
 - com.google.inject.Key.get(com.google.inject.TypeLiteral,java.lang.annotation.Annotation) @bci=6,line=274 (Interpreted frame)
 - com.google.inject.assistedinject.FactoryProvider2.assistKey(java.lang.reflect.Method,com.google.inject.Key,com.google.inject.internal.Errors) @bci=14,line=522 (Interpreted frame)
 - com.google.inject.assistedinject.FactoryProvider2.<init>(com.google.inject.Key,com.google.inject.assistedinject.BindingCollector) @bci=306,line=235 (Interpreted frame)

正如你所看到的,格式是完全不同的,而且是次等的.它不会报告它所持有的锁,也不会报告它正在等待的对象.

有谁知道什么样的JavaVM系列产生第二种堆栈跟踪样式?我自己从未使用过,这一直困扰着我!

解决方法

这是使用-F选项运行时jstack(在Oracle JDK中)的输出.
原文链接:https://www.f2er.com/jvm/130087.html

猜你在找的JVM相关文章