[Jdbc-commits] pgjdbc: Multiple calls to XAConnection.getConnection within the same

[User Jurka]

Log Message:
-----------
Multiple calls to XAConnection.getConnection within the same user
transaction ended up restarting the transaction on the server side
as a result of manipulating the autocommit state.  When retrieving
a Connection, we must pay attention to whether a user transaction
is in progress when setting the autocommit state.

This only fixes the case where a close call is interspersed between
the getConnection calls.  Without the close call, the second
getConnection performs a silent rollback.  Even with the close, this
is dodgy behavior from the client and we expect it not to happen,
but it would be better if we actually forbade it.

Heikki Linnakangas

Tags:
----
REL8_2_STABLE

Modified Files:
--------------
    pgjdbc/org/postgresql/ds/jdbc23:
        AbstractJdbc23PooledConnection.java (r1.1 -> r1.1.2.1)
        (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/ds/jdbc23/AbstractJdbc23PooledConnection.java.diff?r1=1.1&r2=1.1.2.1)
    pgjdbc/org/postgresql/test/xa:
        XADataSourceTest.java (r1.8.2.1 -> r1.8.2.2)
        (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/test/xa/XADataSourceTest.java.diff?r1=1.8.2.1&r2=1.8.2.2)
    pgjdbc/org/postgresql/xa:
        PGXAConnection.java (r1.10.2.1 -> r1.10.2.2)
        (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/jdbc/pgjdbc/org/postgresql/xa/PGXAConnection.java.diff?r1=1.10.2.1&r2=1.10.2.2)