[jira] [Resolved] (GEODE-5401) Client transaction should not be expired once it is failed over

["Eric Shu (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GEODE-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Shu resolved GEODE-5401.
-----------------------------
       Resolution: Fixed
    Fix Version/s: 1.7.0

> Client transaction should not be expired once it is failed over
> ---------------------------------------------------------------
>
>                 Key: GEODE-5401
>                 URL: https://issues.apache.org/jira/browse/GEODE-5401
>             Project: Geode
>          Issue Type: Bug
>          Components: transactions
>    Affects Versions: 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0
>            Reporter: Eric Shu
>            Assignee: Eric Shu
>            Priority: Major
>              Labels: pull-request-available, swat
>             Fix For: 1.7.0
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> When a client is disconnected from the server, the client's originated transactions are scheduled to be expired. However, when the client transaction failed over, the expire transaction task is not cancelled. If transaction is not finished/committed within the timeout period (transactionTimeToLive default to 180 seconds), the transaction will be expired. 
> The consequence is that only part of the transaction gets committed. The expire transaction task will close the transaction and remove it from the hosted txstates map removing the existing operations. The subsequent operations will starts a new transaction -- only the operations afterwards will be recored and committed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)