[
https://issues.apache.org/jira/browse/GEODE-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277381#comment-16277381
]
ASF subversion and git services commented on GEODE-4033:
--------------------------------------------------------
Commit f504c7d607a405fcd156092d050df2edc33e4642 in geode's branch
refs/heads/develop from [~agingade]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f504c7d ]
GEODE-4033: Exception is thrown when Tx Id is not found on server dur… (#1115)
* GEODE-4033: Exception is thrown when Tx Id is not found on server during
failover
> 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
>
> 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
(v6.4.14#64029)
