[infinispan-issues] [JBoss JIRA] Resolved: (ISPN-596) Deadlock detection and explicit locking should be disallowed.
Mircea Markus (JIRA)
jira-events at lists.jboss.org
Thu Aug 12 10:55:49 EDT 2010
[ https://jira.jboss.org/browse/ISPN-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mircea Markus resolved ISPN-596.
--------------------------------
Resolution: Done
resolved
> Deadlock detection and explicit locking should be disallowed.
> -------------------------------------------------------------
>
> Key: ISPN-596
> URL: https://jira.jboss.org/browse/ISPN-596
> Project: Infinispan
> Issue Type: Bug
> Components: Core API, Transactions
> Affects Versions: 4.1.0.CR2
> Reporter: Manik Surtani
> Assignee: Mircea Markus
> Fix For: 4.1.0.CR3, 4.1.0.Final
>
>
> This is temporary, until ISPN-518 is closed. After that, lock() and deadlock detection should be allowed again.
> This needs to be disallowed in 2 places:
> 1) Declarative, implicit eager locking, in ConfigurationValidatingVisitor
> 2) Programmatic, explicit eager locking using the AdvancedCache.lock() API
> should throw a ConfigurationException in both cases, with a message pointing to ISPN-518.
--
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
More information about the infinispan-issues
mailing list