[jira] [Commented] (IGNITE-6445) IgniteTxManager.txLocksInfo method misses locks

["Andrey Gura (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187982#comment-16187982 ] 

Andrey Gura commented on IGNITE-6445:
-------------------------------------

[~VitaliyB] I've looked to your changes and don't see relation between changes and description. At first sight only txs order is changed in {{txLockInfos}} method. From my point of view it shouldn't affect the result. It would be great if you provide reproducer/tests that fails without fix and doesn't fail after fix?

> IgniteTxManager.txLocksInfo method misses locks
> -----------------------------------------------
>
>                 Key: IGNITE-6445
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6445
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.2
>            Reporter: Vitaliy Biryukov
>            Assignee: Vitaliy Biryukov
>             Fix For: 2.3
>
>
> In some cases "IgniteTxManager.txLocksInfo" method (searches for locks) misses locks.
> For example:
> # In case of a configuration with near cache, entries are created for the near cache and for the ordinal cache. For each entry, their own MVCC candidates are created.
> # For non-custom objects of type (Integer, etc.), the entry stored in "GridNearTxLocal" is not associated with MVCC candidates with which the same entity is associated in another format stored in "GridDhtTxLocal"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)