geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anilkumar Gingade (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GEODE-4033) TxFailover doesn't throw exception when tx state is not found on the server
Date Mon, 04 Dec 2017 20:02:00 GMT

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

Anilkumar Gingade updated GEODE-4033:
-------------------------------------
    Fix Version/s: 1.4.0

> 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
>             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
(v6.4.14#64029)

Mime
View raw message