問題描述

如果java層面發生了死鎖，當我們使用jstack命令的時候其實是可以將死鎖的信息給dump出來的，在dump結果的最后會有類似Found one Java-level deadlock:的關鍵字，接著會把發生死鎖的線程的堆棧及對應的同步鎖給打印出來，這次碰到一個系統就發生類似的問題，不過這個dump文檔里雖然提到了如下的死鎖信息：

1 2 3 4 5 6 7 8 9 10 11

Found one Java-level deadlock: ============================= "worker-1-thread-121": waiting to lock monitor 0x00007f3758209dc8 (object 0x0000000764cd2b20, a java.util.concurrent.ConcurrentHashMap), which is held by "HSFBizProcessor-4-thread-4" "HSFBizProcessor-4-thread-4": waiting to lock monitor 0x00007f3758289260 (object 0x000000076073ddc8, a com.alipay.cloudengine.extensions.equinox.KernelBundleClassLoader), which is held by "HSFBizProcessor-4-thread-5" "HSFBizProcessor-4-thread-5": waiting to lock monitor 0x00007f3758253420 (object 0x00000007608e6fc8, a com.alipay.cloudengine.extensions.equinox.KernelBundleClassLoader), which is held by "HSFBizProcessor-4-thread-4"

但是我們在堆棧里搜索對應的鎖的時候并沒發現，也就是上面提到的

1	object 0x00000007608e6fc8 which is held by "HSFBizProcessor-4-thread-4"

我們在HSFBizProcessor-4-thread-4這個線程的堆棧里并沒有看到對應的持鎖信息。

附上線程dump詳情

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69

Found one Java-level deadlock: ============================= "worker-1-thread-121": waiting to lock monitor 0x00007f3758209dc8 (object 0x0000000764cd2b20, a java.util.concurrent.ConcurrentHashMap), which is held by "HSFBizProcessor-4-thread-4" "HSFBizProcessor-4-thread-4": waiting to lock monitor 0x00007f3758289260 (object 0x000000076073ddc8, a com.alipay.cloudengine.extensions.equinox.KernelBundleClassLoader), which is held by "HSFBizProcessor-4-thread-5" "HSFBizProcessor-4-thread-5": waiting to lock monitor 0x00007f3758253420 (object 0x00000007608e6fc8, a com.alipay.cloudengine.extensions.equinox.KernelBundleClassLoader), which is held by "HSFBizProcessor-4-thread-4" Java stack information for the threads listed above: =================================================== "worker-1-thread-121": at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:180) - waiting to lock <0x0000000764cd2b20> (a java.util.concurrent.ConcurrentHashMap) at org.springframework.beans.factory.support.AbstractBeanFactory.isTypeMatch(AbstractBeanFactory.java:455) at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanNamesForType(DefaultListableBeanFactory.java:317) ...... at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.

總結

以上是生活随笔為你收集整理的消失的死锁的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。