On Mon, 2 Oct 2006, Heikki Linnakangas wrote:
> Jan de Visser ran into problems with our XA implementation earlier, and
> traced the problem to the sequence of XADataSource method calls that WebLogic
> performed. He fixed it with a simple patch that allows start(.., TMJOIN) on a
> transaction that was ended earlier using the same connection:
>
> http://archives.postgresql.org/pgsql-jdbc/2005-12/msg00038.php
>
> It puzzles me why WebLogic does that, but it seems valid and we should
> support it, even though we can't support join in general.
>
> Here's a more polished version of Jan's patch. I don't have WebLogic to test
> this with, so I would appreciate if those that have access to WebLogic could
> reproduce the original problem and confirm that this patch fixes it.
>
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.
Kris Jurka
