Re: XA end then join fix for WebLogic - Mailing list pgsql-jdbc

From Kris Jurka
Subject Re: XA end then join fix for WebLogic
Date
Msg-id Pine.BSO.4.64.0612010728090.20488@leary2.csoft.net
Whole thread Raw
In response to Re: XA end then join fix for WebLogic  ("Heikki Linnakangas" <heikki@enterprisedb.com>)
Responses Re: XA end then join fix for WebLogic  (Jan de Visser <jdevisser@digitalfairway.com>)
List pgsql-jdbc

On Fri, 1 Dec 2006, Heikki Linnakangas wrote:

> Kris Jurka wrote:
>> Doesn't this allow:
>>
>> xaRes.start(xid, XAResource.TMNOFLAGS);
>> xaRes.end(xid, XAResource.TMFAIL);
>> xaRes.start(xid, XAResource.TMJOIN);
>> xaRes.end(xid, XAResource.TMSUCCESS);
>> xaRes.commit(xid, true);
>>
>> Is that actually a problem or do we assume the TM is smart enough not to do
>> this.
>
> Hmm, true, it does allow that.
>
> The TM really shouldn't be doing that. It's very confused if it does.
> However, given the sorry state of many TMs out there, it'd be nice if we did
> check for that.
>
> I'd say let's not bother checking that for now. In the future, we should roll
> back the transaction on end(TMFAIL) immediately, and add checking for that
> case as well. The way it works now is perfectly correct and legal, we're just
> not taking advantage of the hint the TM is giving us.
>

OK.  Applied.

Kris Jurka


pgsql-jdbc by date:

Previous
From: Tore Halset
Date:
Subject: setBlob/getBlob, slony and bytea
Next
From: Kris Jurka
Date:
Subject: Re: release for 8.2