Mailing-List: contact issues-help@geode.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geode.apache.org
Date: Mon, 4 Dec 2017 19:51:00 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: issues@geode.apache.org
Message-ID: <JIRA.13121766.1511997089000.381572.1512417060227@Atlassian.JIRA>
In-Reply-To: <JIRA.13121766.1511997089000@Atlassian.JIRA>
References: <JIRA.13121766.1511997089000@Atlassian.JIRA> <JIRA.13121766.1511997089973@jira-lw-us.apache.org>
Subject: [jira] [Commented] (GEODE-4033) TxFailover doesn't throw exception
 when tx state is not found on the server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Mon, 04 Dec 2017 19:51:05 -0000


    [ https://issues.apache.org/jira/browse/GEODE-4033?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1627=
7380#comment-16277380 ]=20

ASF subversion and git services commented on GEODE-4033:
--------------------------------------------------------

Commit f504c7d607a405fcd156092d050df2edc33e4642 in geode's branch refs/head=
s/develop from [~agingade]
[ https://gitbox.apache.org/repos/asf?p=3Dgeode.git;h=3Df504c7d ]

GEODE-4033: Exception is thrown when Tx Id is not found on server dur=E2=80=
=A6 (#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 serv=
er
> -------------------------------------------------------------------------=
--
>
>                 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 server=
s; if not an exception thrown back to the client.=20
> Currently the client catches this exception and tries to re-create the ex=
ception instead of returning back to the application. This could cause mult=
iple transaction state to be created for the same transaction id on the clu=
ster (if the first attempt to the server is still in process), causing unex=
pected behavior.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)