[infinispan-issues] [JBoss JIRA] (ISPN-2728) AbstractCacheTransaction.hasLockOrIsLockBackup may cause NPE

[Radim Vansa (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748937#comment-12748937 ] 

Radim Vansa commented on ISPN-2728:
-----------------------------------

Nope, because the command which calls the hasLock... method belongs to different transaction, which is just waiting until older transactions finish.
                
> AbstractCacheTransaction.hasLockOrIsLockBackup may cause NPE
> ------------------------------------------------------------
>
>                 Key: ISPN-2728
>                 URL: https://issues.jboss.org/browse/ISPN-2728
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Locking and Concurrency, Transactions
>    Affects Versions: 5.2.0.CR1
>            Reporter: Radim Vansa
>            Assignee: Mircea Markus
>
> {{AbstractCacheTransaction.hasLockOrIsLockBackup}} can be called from non-synchronized context (particularly from the {{AbstractTxLockingInterceptor}} when iterating through all transactions from older topology). If the transaction is committed in parallel, {{AbstractCacheTransaction.clearLockedKeys}} is called which nulls the volatile field {{lockedKeys}}.
> {code}
> lockedKeys != null && lockedKeys.contains(key)
> {code}
> Contains a race condition - lockedKey may be nulled between the checks.
> Similar with {{backupKeyLocks}} but these are never nulled.

--
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