| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Jan de Visser <jdevisser(at)digitalfairway(dot)com> |
| Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: XA end then join fix for WebLogic |
| Date: | 2006-10-30 18:32:31 |
| Message-ID: | Pine.BSO.4.63.0610301332040.2855@leary2.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Mon, 2 Oct 2006, Jan de Visser wrote:
> On Monday 02 October 2006 07:46, 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.
>
> I'll have a look "soon". Any deadlines?
>
Did you find the time to do any testing?
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2006-10-30 18:40:14 | Re: confused about transactions and connection pools |
| Previous Message | Kris Jurka | 2006-10-30 18:30:53 | Re: Query ResultSet parsing speedup patch (resend) |