Java虚拟机工具之堆栈跟踪工具jstack检测对象wait方法
来源:互联网 发布:点o是什么文件 linux 编辑:程序博客网 时间:2024/06/03 12:32
wait()方法源于Object类,当线程调用wait的时候,意思就是说线程会放弃对象锁,进入等待此对象的等待锁定池。
下面看看用jstack怎么定位wait方法。
首先写一段简单的调用wait的代码:
import java.util.concurrent.ExecutorService;import java.util.concurrent.Executors;class WaitTask implements Runnable{ @Override public void run(){ synchronized (this) { try{ wait(); }catch (InterruptedException e) { e.printStackTrace(); } } }}public class ThreadWait{ public static void main(String[] args) { WaitTask waitTask = new WaitTask(); ExecutorService executorService = Executors.newFixedThreadPool(1); executorService.execute(waitTask); }}
通过jps找到对应进程的id,然后用jstack跟踪一下:
$ jstack -l 303942016-11-07 16:36:47Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.101-b13 mixed mode):"Attach Listener" #12 daemon prio=9 os_prio=0 tid=0x00007fd2e4001000 nid=0x76ff runnable [0x0000000000000000] java.lang.Thread.State: RUNNABLE Locked ownable synchronizers: - None"DestroyJavaVM" #11 prio=5 os_prio=0 tid=0x00007fd32400a800 nid=0x76bb waiting on condition [0x0000000000000000] java.lang.Thread.State: RUNNABLE Locked ownable synchronizers: - None"pool-1-thread-1" #10 prio=5 os_prio=0 tid=0x00007fd324145000 nid=0x76d1 in Object.wait() [0x00007fd30a4da000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x00000000ec2174e8> (a WaitTask) at java.lang.Object.wait(Object.java:502) at WaitTask.run(ThreadWait.java:13) - locked <0x00000000ec2174e8> (a WaitTask) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Locked ownable synchronizers: - <0x00000000ec2b3758> (a java.util.concurrent.ThreadPoolExecutor$Worker)"Monitor Ctrl-Break" #9 daemon prio=5 os_prio=0 tid=0x00007fd324142000 nid=0x76c9 runnable [0x00007fd30aaf3000] java.lang.Thread.State: RUNNABLE at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:409) at java.net.ServerSocket.implAccept(ServerSocket.java:545) at java.net.ServerSocket.accept(ServerSocket.java:513) at com.intellij.rt.execution.application.AppMain$1.run(AppMain.java:90) at java.lang.Thread.run(Thread.java:745) Locked ownable synchronizers: - None"Service Thread" #8 daemon prio=9 os_prio=0 tid=0x00007fd3240c8800 nid=0x76c7 runnable [0x0000000000000000] java.lang.Thread.State: RUNNABLE Locked ownable synchronizers: - None"C1 CompilerThread2" #7 daemon prio=9 os_prio=0 tid=0x00007fd3240bd000 nid=0x76c6 waiting on condition [0x0000000000000000] java.lang.Thread.State: RUNNABLE Locked ownable synchronizers: - None"C2 CompilerThread1" #6 daemon prio=9 os_prio=0 tid=0x00007fd3240bb800 nid=0x76c5 waiting on condition [0x0000000000000000] java.lang.Thread.State: RUNNABLE Locked ownable synchronizers: - None"C2 CompilerThread0" #5 daemon prio=9 os_prio=0 tid=0x00007fd3240b8800 nid=0x76c4 waiting on condition [0x0000000000000000] java.lang.Thread.State: RUNNABLE Locked ownable synchronizers: - None"Signal Dispatcher" #4 daemon prio=9 os_prio=0 tid=0x00007fd3240b7000 nid=0x76c3 runnable [0x0000000000000000] java.lang.Thread.State: RUNNABLE Locked ownable synchronizers: - None"Finalizer" #3 daemon prio=8 os_prio=0 tid=0x00007fd324084000 nid=0x76c2 in Object.wait() [0x00007fd30bdfc000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x00000000ec188ee0> (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143) - locked <0x00000000ec188ee0> (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:164) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:209) Locked ownable synchronizers: - None"Reference Handler" #2 daemon prio=10 os_prio=0 tid=0x00007fd32407f800 nid=0x76c1 in Object.wait() [0x00007fd30befd000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x00000000ec186b50> (a java.lang.ref.Reference$Lock) at java.lang.Object.wait(Object.java:502) at java.lang.ref.Reference.tryHandlePending(Reference.java:191) - locked <0x00000000ec186b50> (a java.lang.ref.Reference$Lock) at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:153) Locked ownable synchronizers: - None"VM Thread" os_prio=0 tid=0x00007fd324078000 nid=0x76c0 runnable "GC task thread#0 (ParallelGC)" os_prio=0 tid=0x00007fd32401f800 nid=0x76bc runnable "GC task thread#1 (ParallelGC)" os_prio=0 tid=0x00007fd324021000 nid=0x76bd runnable "GC task thread#2 (ParallelGC)" os_prio=0 tid=0x00007fd324023000 nid=0x76be runnable "GC task thread#3 (ParallelGC)" os_prio=0 tid=0x00007fd324024800 nid=0x76bf runnable "VM Periodic Task Thread" os_prio=0 tid=0x00007fd3240cb000 nid=0x76c8 waiting on condition JNI global references: 15
这一段表示jstack已经检测到了wait()正在执行。
"Finalizer" #3 daemon prio=8 os_prio=0 tid=0x00007fd324084000 nid=0x76c2 in Object.wait() [0x00007fd30bdfc000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x00000000ec188ee0> (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143) - locked <0x00000000ec188ee0> (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:164) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:209) Locked ownable synchronizers: - None"Reference Handler" #2 daemon prio=10 os_prio=0 tid=0x00007fd32407f800 nid=0x76c1 in Object.wait() [0x00007fd30befd000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x00000000ec186b50> (a java.lang.ref.Reference$Lock) at java.lang.Object.wait(Object.java:502) at java.lang.ref.Reference.tryHandlePending(Reference.java:191) - locked <0x00000000ec186b50> (a java.lang.ref.Reference$Lock) at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:153) Locked ownable synchronizers: - None
0 0
- Java虚拟机工具之堆栈跟踪工具jstack检测对象wait方法
- Java虚拟机工具之堆栈跟踪工具jstack检测死锁
- Java虚拟机工具之堆栈跟踪工具jstack检测输入等待
- jstack:JAVA堆栈跟踪工具
- jstack:Java堆栈跟踪工具
- Java虚拟机工具之堆栈跟踪工具jstack定位死循环
- Java虚拟机调优工具 jstack
- JVM堆栈跟踪之Jstack命令
- JVM堆栈跟踪之Jstack命令
- 编程工具系列之 ------使用GDB的堆栈跟踪功能
- Java多线程--线程的监控工具之jstack,jvisualvm
- java虚拟机内存监控工具jps,jinfo,Jstack,jstat,jmap,jhat使用
- Java虚拟机工具之虚拟机进程状况工具jps
- Java虚拟机工具之虚拟机统计监控工具jstat
- jstack 命令跟踪 java 应用的堆栈 并分析堆栈结果
- Java内存泄露监控工具:jconsole, jstack
- Java线程查看工具——jstack
- Java线程Dump分析工具--jstack
- 简单分析hashmap 中的entryset()方法
- oracle数据库启动报错ORA-12560问题解决方法
- MFC大神之路
- Vue.js结合vue-router和webpack编写单页路由项目
- R语言技巧:对读取常用的集中格式的介绍
- Java虚拟机工具之堆栈跟踪工具jstack检测对象wait方法
- 二分查找(BinarySearch)
- P_CalcPlan
- C# 将byte 保存为文件 转为文件
- matlab 大津算法 ostu 程序
- 输入组数未知的数据,c和c++的不一样。
- 谁杀死了MySQL?
- Retrofit简要分析
- 升级到Xcode8遇到的问题