[
https://jira.jboss.org/jira/browse/ISPN-396?page=com.atlassian.jira.plugi...
]
Manik Surtani commented on ISPN-396:
------------------------------------
Yes, this is not a bug, this is normal when you have 2 nodes attempting to acquire the
same lock. Locks are acquired locally first before being acquired remotely, and with some
unfortunate timing this can happen. Try enabling deadlock detection -
http://community.jboss.org/wiki/Infinispantransactions#deadlock
deadlock in distributed lock aquisition
----------------------------------------
Key: ISPN-396
URL:
https://jira.jboss.org/jira/browse/ISPN-396
Project: Infinispan
Issue Type: Bug
Components: Distributed Cache
Reporter: SriNarayanan ThangaNadar
Assignee: Manik Surtani
Attachments: InfiniPri.java, InfiniPri.log, InfiniSec.java, InfiniSec.log,
jgroups-tcp.xml
AdvancedCache transaction waiting indefinitely at commit when another transaction is
waiting to acquire the lock
Both Tx wait resulting in a deadlock
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira