[ https://issues.jboss.org/browse/ISPN-5654?page=com.atlassian.jira.plugin.... ] Dan Berindei edited comment on ISPN-5654 at 2/28/17 6:55 AM: ------------------------------------------------------------- -Looking at the code, the deadlock detection doesn't seem to work at all in most cases. Lock intentions are only added in {{DeadlockDetectingLockManager.lock(key)}}, which doesn't get called on the transaction originator unless it's also the primary owner of the key. Thus lock intentions are never sent from the tx originator to the primary owners, and deadlock detection for multiple keys only works when all the keys are owned by the originator. And of course, same-key deadlocks cannot happen at all with the single-node locking.- I propose to remove {{DeadlockDetectingLockManager}} altogether and to deprecate the related configuration. was (Author: dan.berindei): Looking at the code, the deadlock detection doesn't seem to work at all in most cases. Lock intentions are only added in {{DeadlockDetectingLockManager.lock(key)}}, which doesn't get called on the transaction originator unless it's also the primary owner of the key. Thus lock intentions are never sent from the tx originator to the primary owners, and deadlock detection for multiple keys only works when all the keys are owned by the originator. And of course, same-key deadlocks cannot happen at all with the single-node locking. I propose to remove {{DeadlockDetectingLockManager}} altogether and to deprecate the related configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)