标签:witelock PrintConcurrentLocks Java lock XX locks 死锁 does deadlock
Refr to https://josephmate.github.io/2020-02-24-deadlock-who-owns-the-lock/
What I Learned
- Locking a readlock, then locking the write lock on the same lock creates a deadlock.
- Deadlocks created using locks instead of monitors does not appear in thread dumps (like those created by kill -3 (linux) or Ctrl+Break (windows)).
- Keep digging and you’ll uncover a nasty incorrect assumption you’ve been making.
-XX:+PrintConcurrentLocks
detects some deadlocks-XX:+PrintConcurrentLocks
does not print reentrant locks on stack traces-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
本站声明: 1. iCode9 技术分享网(下文简称本站)提供的所有内容,仅供技术学习、探讨和分享; 2. 关于本站的所有留言、评论、转载及引用,纯属内容发起人的个人观点,与本站观点和立场无关; 3. 关于本站的所有言论和文字,纯属内容发起人的个人观点,与本站观点和立场无关; 4. 本站文章均是网友提供,不完全保证技术分享内容的完整性、准确性、时效性、风险性和版权归属;如您发现该文章侵犯了您的权益,可联系我们第一时间进行删除; 5. 本站为非盈利性的个人网站,所有内容不会用来进行牟利,也不会利用任何形式的广告来间接获益,纯粹是为了广大技术爱好者提供技术内容和技术思想的分享性交流网站。