[ https://issues.apache.org/jira/browse/IGNITE-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vitaliy Biryukov updated IGNITE-6445: ------------------------------------- Fix Version/s: (was: 2.7) 2.8 > 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 > Priority: Major > Fix For: 2.8 > > > 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 (v7.6.3#76005)