manual transaction for all JDBC calls

[Toby Davis]

For consistency, I usually have autocommit set to false for all my JDBC calls. I know when it's necessary to have for complex transactions, such as multiple batch queries, insert/update/delete calls and so forth.
Is there any performance hit or other issues using manual transactions for single calls (see example below)?
Simple example:

/* assume dataSource has already been instantiated from app server named datasource */
Connection con = null;
CallableStatement cs = null;
ResultSet rs = null;
    try {
        con = dataSource.getConnection();
        con.setAutoCommit(false);
        cs = con.prepareCall("{ call aSelectStoredProc(?, ?) }");
        cs.setString(1, strVal);
        cs.setInt(2, intVal);
        rs = cs.executeQuery();
        while (rs.next()) {
            // code to handle resultset
        }
        con.commit();
    } catch {
        con.rollback();
        // then throw whatever exception that the containing method allows
    } finally {
        if (rs != null) {
            rs.close();
        }
        if (cs != null) {
            cs.close();
        }
        if (con != null) {
            con.close();
        }
    }

[Adam Hardy]

There's no performance hit - in fact if you save up your commits until the end of all the db calls, you can get a performance gain, since you only do one commit, compared to autocommit which does a commit for every statement.

Adam