| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Allan Saddi <allan(at)saddi(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: XA transactions and autocommit |
| Date: | 2006-12-01 10:14:49 |
| Message-ID: | Pine.BSO.4.64.0612010514001.31193@leary2.csoft.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Sat, 7 Oct 2006, Allan Saddi wrote:
> I've been playing around with JTA using Apache Geronimo and the
> postgresql-8.1-407.jdbc3.jar driver. I've noticed a minor problem. The
> driver's XA code disables autocommit and assumes it will remain so
> indefinitely. tranql-connection (used by Geronimo for pooling) enables
> autocommit whenever the connection is returned to the pool. (Specifically in
> its ManagedXAConnection.cleanup method.) According to the J2EE Connector
> spec, this is apparently the correct thing to do.
>
> I've made a minor patch against 407 that does just this. XAResource.start
> disables autocommit, and autocommit is then re-enabled at the appropriate
> place within the prepare, commit, and rollback methods.
>
Patch applied, thanks.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2006-12-01 10:47:21 | Re: Authentication trick |
| Previous Message | Csaba Nagy | 2006-12-01 09:35:37 | Re: Backup with Java |