[
https://issues.apache.org/jira/browse/IGNITE-10509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709738#comment-16709738
]
Anton Kalashnikov commented on IGNITE-10509:
--------------------------------------------
[~DmitriyGovorukhin], you actually right, but I don't ready to add
synchronization on state and timeout now because it looks like too redundantly.
But my changes looks correct because timeout is reason of state changing but
state changing is not reason of timeout.
If you have any other idea, please share it.
> 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)
