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

标签：witelock,PrintConcurrentLocks,Java,lock,XX,locks,死锁,does,deadlock
来源： https://www.cnblogs.com/tang88seng/p/16260257.html