You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/12/03 13:51:00 UTC

[jira] [Commented] (IGNITE-10509) Rollback exception instead of timeout exception

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

ASF GitHub Bot commented on IGNITE-10509:
-----------------------------------------

GitHub user akalash opened a pull request:

    https://github.com/apache/ignite/pull/5555

    IGNITE-10509 reordered setting of timeout flag and transaction state

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-10509

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/5555.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #5555
    
----
commit ada8fc9cb664e70f975312007f9d5003ca6a82b0
Author: Anton Kalashnikov <ka...@...>
Date:   2018-12-03T13:49:24Z

    IGNITE-10509 reordered setting of timeout flag and transaction state

----


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