Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (nike.apache.org: domain of genspring@gmail.com designates
 209.85.212.54 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=lMMhbLpLZCTWJA62YCbHuVhfA+v0M/ISnwP08UyzF78LTyB32imzK4Ho5F0+3oQJ3y
         WVUaWi+9/UOk9/ny2rup32ZU7khz7H0k8eXGilbDFjWRRYY3RzkVkinQP0kDN0eJvVcr
         tSGPGmtL2lfR9nHlGHFIKShaSeH2SPGFf9QXU=
MIME-Version: 1.0
In-Reply-To: <4415944.16521287381145584.JavaMail.jira@thor>
References: <20390966.11211287345202376.JavaMail.jira@thor>
	<4415944.16521287381145584.JavaMail.jira@thor>
Date: Tue, 19 Oct 2010 14:50:49 +0800
Message-ID: <AANLkTi=iP2e9Gh9Et2yPBa293Y+adD8NuURqJnb57cOk@mail.gmail.com>
Subject: Re: [jira] Updated: (GERONIMO-5649) txmanager could try to replace
 dead XAResources in commit and rollback tasks
From: Shawn Jiang <genspring@gmail.com>
To: dev@geronimo.apache.org
Content-Type: multipart/alternative; boundary=90e6ba53abb48aa11a0492f2b684

--90e6ba53abb48aa11a0492f2b684
Content-Type: text/plain; charset=ISO-8859-1

Shall we include this fix into the coming 2.2.1 release  ?

On Mon, Oct 18, 2010 at 1:52 PM, David Jencks (JIRA) <jira@apache.org>wrote:

>
>     [
> https://issues.apache.org/jira/browse/GERONIMO-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> David Jencks updated GERONIMO-5649:
> -----------------------------------
>
>     Attachment: GERONIMO-5649-2.patch
>
> Fixes tx state and a connection leak when we have to get a new connection
> to retry commit/rollback.
>
> > txmanager could try to replace dead XAResources in commit and rollback
> tasks
> >
> ----------------------------------------------------------------------------
> >
> >                 Key: GERONIMO-5649
> >                 URL: https://issues.apache.org/jira/browse/GERONIMO-5649
> >             Project: Geronimo
> >          Issue Type: Bug
> >      Security Level: public(Regular issues)
> >          Components: transaction manager
> >    Affects Versions: 2.2, 3.0
> >            Reporter: David Jencks
> >            Assignee: David Jencks
> >             Fix For: 2.2.1, 3.0
> >
> >         Attachments: GERONIMO-5649-1.patch, GERONIMO-5649-2.patch
> >
> >
> > Generally if a RM crashes, outbound connections to it need to be
> reestablished.  So if we have a in-doubt tx using an outbound connection, we
> should try to get a new XAResource to finish up the branch in the CommitTask
> and proposed RollbackTask.
> > AFAIK inbound connections will automatically reestablish connections and
> use the RETRY error code so we don't need to do this for inbound.  I still
> need to find out which error codes indicate that we should get a new
> connection and try again.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>


-- 
Shawn

--90e6ba53abb48aa11a0492f2b684
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Shall we include this fix into the coming 2.2.1 release=A0 ?=A0 <br><br><di=
v class=3D"gmail_quote">On Mon, Oct 18, 2010 at 1:52 PM, David Jencks (JIRA=
) <span dir=3D"ltr">&lt;<a href=3D"mailto:jira@apache.org">jira@apache.org<=
/a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class=3D"im"=
><br>
 =A0 =A0 [ <a href=3D"https://issues.apache.org/jira/browse/GERONIMO-5649?p=
age=3Dcom.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" target=
=3D"_blank">https://issues.apache.org/jira/browse/GERONIMO-5649?page=3Dcom.=
atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a> ]<br>

<br>
David Jencks updated GERONIMO-5649:<br>
-----------------------------------<br>
<br>
</div> =A0 =A0Attachment: GERONIMO-5649-2.patch<br>
<br>
Fixes tx state and a connection leak when we have to get a new connection t=
o retry commit/rollback.<br>
<div class=3D"im"><br>
&gt; txmanager could try to replace dead XAResources in commit and rollback=
 tasks<br>
&gt; ----------------------------------------------------------------------=
------<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Key: GERONIMO-5649<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 URL: <a href=3D"https://issues.apache.=
org/jira/browse/GERONIMO-5649" target=3D"_blank">https://issues.apache.org/=
jira/browse/GERONIMO-5649</a><br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 Project: Geronimo<br>
&gt; =A0 =A0 =A0 =A0 =A0Issue Type: Bug<br>
&gt; =A0 =A0 =A0Security Level: public(Regular issues)<br>
&gt; =A0 =A0 =A0 =A0 =A0Components: transaction manager<br>
&gt; =A0 =A0Affects Versions: 2.2, 3.0<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0Reporter: David Jencks<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0Assignee: David Jencks<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 Fix For: 2.2.1, 3.0<br>
&gt;<br>
</div>&gt; =A0 =A0 =A0 =A0 Attachments: GERONIMO-5649-1.patch, GERONIMO-564=
9-2.patch<br>
<div><div></div><div class=3D"h5">&gt;<br>
&gt;<br>
&gt; Generally if a RM crashes, outbound connections to it need to be reest=
ablished. =A0So if we have a in-doubt tx using an outbound connection, we s=
hould try to get a new XAResource to finish up the branch in the CommitTask=
 and proposed RollbackTask.<br>

&gt; AFAIK inbound connections will automatically reestablish connections a=
nd use the RETRY error code so we don&#39;t need to do this for inbound. =
=A0I still need to find out which error codes indicate that we should get a=
 new connection and try again.<br>

<br>
--<br>
This message is automatically generated by JIRA.<br>
-<br>
You can reply to this email to add a comment to the issue online.<br>
<br>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>Shawn<br>

--90e6ba53abb48aa11a0492f2b684--