Re: JPA + Postgres = autocommit? - Mailing list pgsql-jdbc

From Craig Ringer
Subject Re: JPA + Postgres = autocommit?
Date
Msg-id CAMsr+YERVmwD1fqgb6y=3KOF0zw03+1UNTj0DeCY2CFs4rTi-A@mail.gmail.com
Whole thread Raw
In response to Re: JPA + Postgres = autocommit?  ("Davygora, Yuriy" <Yuriy.Davygora@sulzer.de>)
Responses Re: JPA + Postgres = autocommit?
List pgsql-jdbc
On 27 July 2016 at 16:50, Davygora, Yuriy <Yuriy.Davygora@sulzer.de> wrote:

 

  Hello Lachezar,

 

  thank you for your reply.

 

  First of all, let me list some of the things I had tried before I started digging into the source code of the Postgres JDBC driver and Eclipselink.

 

-          switching PGConnectionPoolDataSource.

-          both container managed and bean managed transactions.

-          REQUIRED and REQUIRES_NEW for container managed transactions.

 

  None of this worked.



IIRC with Glassfish back in the day I used org.postgresql.Driver and let Glassfish's connection pooler wrap its own DataSource around it.


 

  I ruled out the possibility of a bug in the Postgres JDBC driver and in EclipseLink. Only Payara remains. As said, for some reason, setAutoCommit is never called, which is the job of the transaction manager.


Yeah, that's pretty suspect.


--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-jdbc by date:

Previous
From: Thomas Kellerer
Date:
Subject: Re: ResultSet.getClob() causing problems when used with JPA's @Lob
Next
From: Craig Ringer
Date:
Subject: Re: Possible bug related to primary keys autogeneration