[
https://issues.apache.org/jira/browse/IGNITE-10509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709371#comment-16709371
]
Dmitriy Govorukhin commented on IGNITE-10509:
---------------------------------------------
[~akalashnikov] I did review your changes, and I have a question. Why this
reordering solve a problem? I can get timeout status (true), but transaction
state wasn't changed. Why is it ok? I mean, we still have a race between
changes timeout status and change transaction change. Should we change timeout
first in all cases?
> Rollback exception instead of timeout exception
> -----------------------------------------------
>
> Key: IGNITE-10509
> URL: https://issues.apache.org/jira/browse/IGNITE-10509
> Project: Ignite
> Issue Type: Bug
> Reporter: Anton Kalashnikov
> Assignee: Anton Kalashnikov
> Priority: Major
> Fix For: 2.8
>
>
> Looks like we have race on changing transaction state between timedOut and
> state set
> Reproducer - TxRollbackOnTimeoutNearCacheTest.testEnlistManyWrite
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
