[
https://issues.apache.org/jira/browse/GEODE-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564251#comment-16564251
]
ASF subversion and git services commented on GEODE-5401:
--------------------------------------------------------
Commit 6f4c5421fd46e520d29af7156b7171e335e18060 in geode's branch
refs/heads/develop from pivotal-eshu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=6f4c542 ]
GEODE-5401: Check if transaction has been failed over before expiring client
transactions. (#2197)
* Use ExpireDisconnectedClientTransactionsMessage instead of
TXManagerImpl.TXRemovalMessage when expire client transactions.
* Only send new message to Geode 1.7.0 and later servers - assuming old version
servers will be rolled soon.
* Handle differently when server receives this message based on sender version.
> 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, 1.7.0
> Reporter: Eric Shu
> Assignee: Eric Shu
> Priority: Major
> Labels: pull-request-available, swat
> 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)
