From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
Cc: | Luca Ferrari <fluca1978(at)infinito(dot)it>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: a simple example of XA (not working) |
Date: | 2007-07-06 20:35:33 |
Message-ID: | Pine.BSO.4.64.0707061632580.10158@leary.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Mon, 25 Jun 2007, Heikki Linnakangas wrote:
> Kris Jurka wrote:
>>
>> I don't think this fixes the problem completely if you have code that calls
>> XAConnection.getConnection more than once:
>>
>
> You got me at first, but actually the second getConnection call will *roll
> back* the first part of the transaction. See
> AbstractJdbc23PooledConnection.getConnection. I don't think that's a valid
> thing to do in the first place, though we could handle it more gracefully. I
> added a note of that in the comment in PGXAConnection.getConnection anyway.
>
OK. I always have trouble remembering who does what with XA (TM vs
user), so in this case we can rely on the TM getting it right, while I was
thinking we had to prevent the user from getting it wrong.
Applied to 8.1, 8.2, and HEAD.
Kris Jurka
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2007-07-06 20:51:09 | Re: SSL support for javax.sql.DataSource |
Previous Message | Dave Cramer | 2007-07-06 12:28:00 | Re: Connection is closed. Operation is not permitted. ------HELP.... |