Re: XA rollback problem

From: "Niels Beekman" <n(dot)beekman(at)wis(dot)nl>
To: "Kris Jurka" <books(at)ejurka(dot)com>
Cc: <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: XA rollback problem
Date: 2006-04-27 07:51:38
Message-ID: 50CA25BD6EEA954FA592C097399942E30E463E5F@CM1.wis.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Hi Kris,

Thank you very much, it works!

Niels

-----Original Message-----
From: Kris Jurka [mailto:books(at)ejurka(dot)com]
Sent: woensdag 26 april 2006 22:31
To: Niels Beekman
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [JDBC] XA rollback problem

On Mon, 24 Apr 2006, Kris Jurka wrote:

> Indeed the closing before committing is a problem. The PGXADatasource
code
> is piggybacking on the PooledConnection code. When you close a
> PooledConnection a rollback occurs so that the connection can be
reused. For
> the XAConnection it must put the connection into a pending-closed
state and
> wait for the transaction manager to commit or rollback the connection.
It'll
> be a little tricky to make this work for both the PooledConnection and

> XAConnection cases, but I'll take a look at that this week.
>

I have applied the attached patch to the 8.1 and head cvs branches which

fixes it for me.

I've uploaded some jars for you to test here, and a new official release

should hopefully be out within the week.

http://www.ejurka.com/pgsql/jars/nb/

Kris Jurka

Browse pgsql-jdbc by date

  From Date Subject
Next Message Jaime Vizán 2006-04-27 10:38:29 Error 08S01 (COMMUNICATION_ERROR)
Previous Message Kris Jurka 2006-04-26 23:37:01 Re: Bug with callable statement and output parameters