本文主要是介绍Java ReentrantReadWriteLock 同一个线程先 readlock, 再 witelock 死锁 - dead lock，对大家解决编程问题具有一定的参考价值，需要的程序猿们随着小编来一起学习吧！

Refr to https://josephmate.github.io/2020-02-24-deadlock-who-owns-the-lock/

What I Learned

1. Locking a readlock, then locking the write lock on the same lock creates a deadlock.
2. Deadlocks created using locks instead of monitors does not appear in thread dumps (like those created by kill -3 (linux) or Ctrl+Break (windows)).
3. Keep digging and you’ll uncover a nasty incorrect assumption you’ve been making.
4. -XX:+PrintConcurrentLocks detects some deadlocks
5. -XX:+PrintConcurrentLocks does not print reentrant locks on stack traces
6. -XX:+PrintConcurrentLocks does not detect acquiring read then write lock in the same thread deadlock

这篇关于Java ReentrantReadWriteLock 同一个线程先 readlock, 再 witelock 死锁 - dead lock的文章就介绍到这儿，希望我们推荐的文章对大家有所帮助，也希望大家多多支持为之网！