You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Swapnil Bawaskar (JIRA)" <ji...@apache.org> on 2018/02/01 22:52:13 UTC

[jira] [Closed] (GEODE-4033) TxFailover doesn't throw exception when tx state is not found on the server

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

Swapnil Bawaskar closed GEODE-4033.
-----------------------------------

> TxFailover doesn't throw exception when tx state is not found on the server
> ---------------------------------------------------------------------------
>
>                 Key: GEODE-4033
>                 URL: https://issues.apache.org/jira/browse/GEODE-4033
>             Project: Geode
>          Issue Type: Bug
>          Components: transactions
>            Reporter: Anilkumar Gingade
>            Assignee: Anilkumar Gingade
>            Priority: Major
>             Fix For: 1.4.0
>
>
> When a client transaction gets an exception due to connection failure; it tries to execute the transaction on other available server. This failover transaction is processed, if the tx.state is available on any of the servers; if not an exception thrown back to the client. 
> Currently the client catches this exception and tries to re-create the exception instead of returning back to the application. This could cause multiple transaction state to be created for the same transaction id on the cluster (if the first attempt to the server is still in process), causing unexpected behavior.



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