11:26 a.m.
Deadlock detection should be able to used with eager locking
------------------------------------------------------------
Key: ISPN-518
URL: https://jira.jboss.org/browse/ISPN-518
Project: Infinispan
Issue Type: Feature Request
Components: Locking and Concurrency
Affects Versions: 4.1.0.BETA2
Reporter: Erik Salter
Assignee: Manik Surtani
(As described on the forums):
With a cache that explicitly (eagerly) locks a key and deadlock detecting --
If transactions operating on a different node try to lock the same key, Infinispan will
detect the deadlock. However, it can't interrupt the deadlock, so the transaction
ends up timing out.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:39 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-518) Deadlock detection should be able to used with eager locking
[
https://jira.jboss.org/browse/ISPN-518?page=com.atlassian.jira.plugin.sys...
]
Manik Surtani updated ISPN-518:
-------------------------------
Assignee: Mircea Markus (was: Manik Surtani)
Fix Version/s: 4.1.0.CR1
4.1.0.Final
Deadlock detection should be able to used with eager locking
------------------------------------------------------------
Key: ISPN-518
URL: https://jira.jboss.org/browse/ISPN-518
Project: Infinispan
Issue Type: Feature Request
Components: Locking and Concurrency
Affects Versions: 4.1.0.BETA2
Reporter: Erik Salter
Assignee: Mircea Markus
Fix For: 4.1.0.CR1, 4.1.0.Final
(As described on the forums):
With a cache that explicitly (eagerly) locks a key and deadlock detecting --
If transactions operating on a different node try to lock the same key, Infinispan will
detect the deadlock. However, it can't interrupt the deadlock, so the transaction
ends up timing out.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:22 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-518) Deadlock detection should be able to used with eager locking
[
https://jira.jboss.org/browse/ISPN-518?page=com.atlassian.jira.plugin.sys...
]
Mircea Markus commented on ISPN-518:
------------------------------------
Another issue reported here: http://community.jboss.org/message/550607#550607
Deadlock detection should be able to used with eager locking
------------------------------------------------------------
Key: ISPN-518
URL: https://jira.jboss.org/browse/ISPN-518
Project: Infinispan
Issue Type: Feature Request
Components: Locking and Concurrency
Affects Versions: 4.1.0.BETA2
Reporter: Erik Salter
Assignee: Mircea Markus
Fix For: 4.1.0.CR1, 4.1.0.Final
(As described on the forums):
With a cache that explicitly (eagerly) locks a key and deadlock detecting --
If transactions operating on a different node try to lock the same key, Infinispan will
detect the deadlock. However, it can't interrupt the deadlock, so the transaction
ends up timing out.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:53 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-518) Deadlock detection should be able to used with eager locking
[
https://jira.jboss.org/browse/ISPN-518?page=com.atlassian.jira.plugin.sys...
]
Galder Zamarreno updated ISPN-518:
----------------------------------
Fix Version/s: 4.1.0.CR2
(was: 4.1.0.CR1)
Deadlock detection should be able to used with eager locking
------------------------------------------------------------
Key: ISPN-518
URL: https://jira.jboss.org/browse/ISPN-518
Project: Infinispan
Issue Type: Feature Request
Components: Locking and Concurrency
Affects Versions: 4.1.0.BETA2
Reporter: Erik Salter
Assignee: Mircea Markus
Fix For: 4.1.0.CR2, 4.1.0.Final
(As described on the forums):
With a cache that explicitly (eagerly) locks a key and deadlock detecting --
If transactions operating on a different node try to lock the same key, Infinispan will
detect the deadlock. However, it can't interrupt the deadlock, so the transaction
ends up timing out.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:23 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-518) Deadlock detection should be able to used with eager locking
[
https://jira.jboss.org/browse/ISPN-518?page=com.atlassian.jira.plugin.sys...
]
Mircea Markus updated ISPN-518:
-------------------------------
Fix Version/s: 5.1.0.Final
(was: 4.1.0.CR2)
(was: 4.1.0.Final)
Affects Version/s: 4.0.0.Final
(was: 4.1.0.BETA2)
Description:
(As described on the forums):
With a cache that explicitly (eagerly) locks a key and deadlock detecting --
If transactions operating on a different node try to lock the same key, Infinispan will
detect the deadlock. However, it can't interrupt the deadlock, so the transaction
ends up timing out.
was:
(As described on the forums):
With a cache that explicitly (eagerly) locks a key and deadlock detecting --
If transactions operating on a different node try to lock the same key, Infinispan will
detect the deadlock. However, it can't interrupt the deadlock, so the transaction
ends up timing out.
Deadlock detection should be able to used with eager locking
------------------------------------------------------------
Key: ISPN-518
URL: https://jira.jboss.org/browse/ISPN-518
Project: Infinispan
Issue Type: Feature Request
Components: Locking and Concurrency
Affects Versions: 4.0.0.Final
Reporter: Erik Salter
Assignee: Mircea Markus
Fix For: 5.1.0.Final
(As described on the forums):
With a cache that explicitly (eagerly) locks a key and deadlock detecting --
If transactions operating on a different node try to lock the same key, Infinispan will
detect the deadlock. However, it can't interrupt the deadlock, so the transaction
ends up timing out.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:28 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-518) Deadlock detection should be able to used with eager locking
[
https://jira.jboss.org/browse/ISPN-518?page=com.atlassian.jira.plugin.sys...
]
Mircea Markus updated ISPN-518:
-------------------------------
Attachment: eager_locking_work.patch
Patch with eager locking enabled.
Work that still needs to be done:
- parametrize LockingInterceptor.visitLockControlCommand to only do a remote-lock-first
if DLD is enabled
- if remotelock is successful and local lock fails, do a remote unlock (no such command as
yet, needs to be implemented)
Deadlock detection should be able to used with eager locking
------------------------------------------------------------
Key: ISPN-518
URL: https://jira.jboss.org/browse/ISPN-518
Project: Infinispan
Issue Type: Feature Request
Components: Locking and Concurrency
Affects Versions: 4.0.0.Final
Reporter: Erik Salter
Assignee: Mircea Markus
Fix For: 5.1.0.Final
Attachments: eager_locking_work.patch
(As described on the forums):
With a cache that explicitly (eagerly) locks a key and deadlock detecting --
If transactions operating on a different node try to lock the same key, Infinispan will
detect the deadlock. However, it can't interrupt the deadlock, so the transaction
ends up timing out.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:33 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-518) Deadlock detection should be able to used with eager locking
[
https://jira.jboss.org/browse/ISPN-518?page=com.atlassian.jira.plugin.sys...
]
Mircea Markus commented on ISPN-518:
------------------------------------
This is very relevant for further development:
http://lists.jboss.org/pipermail/infinispan-dev/2010-July/005825.html
Deadlock detection should be able to used with eager locking
------------------------------------------------------------
Key: ISPN-518
URL: https://jira.jboss.org/browse/ISPN-518
Project: Infinispan
Issue Type: Feature Request
Components: Locking and Concurrency
Affects Versions: 4.0.0.Final
Reporter: Erik Salter
Assignee: Mircea Markus
Fix For: 5.1.0.Final
Attachments: eager_locking_work.patch
(As described on the forums):
With a cache that explicitly (eagerly) locks a key and deadlock detecting --
If transactions operating on a different node try to lock the same key, Infinispan will
detect the deadlock. However, it can't interrupt the deadlock, so the transaction
ends up timing out.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:06 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-518) Deadlock detection should be able to used with eager locking
[
https://jira.jboss.org/browse/ISPN-518?page=com.atlassian.jira.plugin.sys...
]
Manik Surtani updated ISPN-518:
-------------------------------
Fix Version/s: 4.2.0.BETA1
4.2.0.Final
(was: 5.1.0.Final)
Complexity: High
Deadlock detection should be able to used with eager locking
------------------------------------------------------------
Key: ISPN-518
URL: https://jira.jboss.org/browse/ISPN-518
Project: Infinispan
Issue Type: Feature Request
Components: Locking and Concurrency
Affects Versions: 4.0.0.Final
Reporter: Erik Salter
Assignee: Mircea Markus
Fix For: 4.2.0.BETA1, 4.2.0.Final
Attachments: eager_locking_work.patch
(As described on the forums):
With a cache that explicitly (eagerly) locks a key and deadlock detecting --
If transactions operating on a different node try to lock the same key, Infinispan will
detect the deadlock. However, it can't interrupt the deadlock, so the transaction
ends up timing out.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:19 a.m.
New subject: [JBoss JIRA] Resolved: (ISPN-518) Deadlock detection should be able to used with eager locking
[
https://jira.jboss.org/browse/ISPN-518?page=com.atlassian.jira.plugin.sys...
]
Mircea Markus resolved ISPN-518.
--------------------------------
Resolution: Done
solved
Deadlock detection should be able to used with eager locking
------------------------------------------------------------
Key: ISPN-518
URL: https://jira.jboss.org/browse/ISPN-518
Project: Infinispan
Issue Type: Feature Request
Components: Locking and Concurrency
Affects Versions: 4.0.0.Final
Reporter: Erik Salter
Assignee: Mircea Markus
Fix For: 4.2.0.BETA1, 4.2.0.Final
Attachments: eager_locking_work.patch
(As described on the forums):
With a cache that explicitly (eagerly) locks a key and deadlock detecting --
If transactions operating on a different node try to lock the same key, Infinispan will
detect the deadlock. However, it can't interrupt the deadlock, so the transaction
ends up timing out.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:46 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-518) Deadlock detection should be able to used with eager locking
[
https://jira.jboss.org/browse/ISPN-518?page=com.atlassian.jira.plugin.sys...
]
Mircea Markus updated ISPN-518:
-------------------------------
Fix Version/s: 4.2.0.ALPHA1
(was: 4.2.0.BETA1)
Deadlock detection should be able to used with eager locking
------------------------------------------------------------
Key: ISPN-518
URL: https://jira.jboss.org/browse/ISPN-518
Project: Infinispan
Issue Type: Feature Request
Components: Locking and Concurrency
Affects Versions: 4.0.0.Final
Reporter: Erik Salter
Assignee: Mircea Markus
Fix For: 4.2.0.ALPHA1, 4.2.0.Final
Attachments: eager_locking_work.patch
(As described on the forums):
With a cache that explicitly (eagerly) locks a key and deadlock detecting --
If transactions operating on a different node try to lock the same key, Infinispan will
detect the deadlock. However, it can't interrupt the deadlock, so the transaction
ends up timing out.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5230
days inactive
5299
days old
infinispan-issues@lists.jboss.org
9 comments
4 participants
participants (4)
-
Erik Salter (JIRA) -
Galder Zamarreno (JIRA)
-
Manik Surtani (JIRA)
-
Mircea Markus (JIRA)