postgres jdbc transaction problem surfaces at times - Mailing list pgsql-jdbc

From kevin@mtel.co.uk
Subject postgres jdbc transaction problem surfaces at times
Date
Msg-id 1144856469.014948.89160@j33g2000cwa.googlegroups.com
Whole thread Raw
Responses Re: postgres jdbc transaction problem surfaces at times  (Mark Lewis <mark.lewis@mir3.com>)
List pgsql-jdbc
i read in the posts here that postgres 8.0 jdbc had unmasked it;s
dislike of changing transaction level mid transaction so i changed my
code to the following

is this set up correct?

        try {
            livedb.setAutoCommit(false);
            copydb.setAutoCommit(false);


livedb.setTransactionIsolation(Connection.TRANSACTION_SERIALIZABLE);

            copydb.setTransactionIsolation
(Connection.TRANSACTION_SERIALIZABLE);

            // series of writes to both db's

            livedb.commit();
            livedb.setAutoCommit(true);
            copydb.commit();
            copydb.setAutoCommit(true);

        } catch (SQLException sqle){
                // run a rollback-Release and log it routine;

                // crash and burn;
        }

this seems to work fine single user, but with several users on i get
occasional dumps with
transaction change in transaction.

the only code to change relates to the LUW start since the last rollout
of this servlet and there was never this problem before.
the connections are stored as a session attribute, so persist across
requests.


pgsql-jdbc by date:

Previous
From: Oliver Jowett
Date:
Subject: Re: No automatic reconnect after network error
Next
From: Mark Lewis
Date:
Subject: Re: postgres jdbc transaction problem surfaces at times