[infinispan-issues] [JBoss JIRA] (ISPN-2491) Order of locks in optimistic locking is not strict

Mircea Markus (JIRA) jira-events at lists.jboss.org
Wed Nov 21 06:09:22 EST 2012


     [ https://issues.jboss.org/browse/ISPN-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mircea Markus updated ISPN-2491:
--------------------------------

    Fix Version/s: 6.0.0.Final

    
> Order of locks in optimistic locking is not strict
> --------------------------------------------------
>
>                 Key: ISPN-2491
>                 URL: https://issues.jboss.org/browse/ISPN-2491
>             Project: Infinispan
>          Issue Type: Quality Risk
>          Components: Locking and Concurrency
>    Affects Versions: 5.2.0.Beta3, 5.1.8.Final
>            Reporter: Radim Vansa
>            Assignee: Mircea Markus
>            Priority: Minor
>             Fix For: 6.0.0.Final
>
>
> In OptimisticLockingInterceptor, the keys are ordered according to their hash. However, the hashes can still collide, which may result in a deadlock if two keys with identical hash (only 32-bit) are sorted to different order. We should try to check if the keys are Comparable or let user provide some comparator class in config, and use the compare of hash only as the last resort.
> In all cases, a warning should be emitted if the compare operation had non-strict result.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the infinispan-issues mailing list