java.sql.Connection - does not throw SQLException on calling commit() or rollback() - in AutoCommit

[Vinay Kumar T M]

Hi,

This query is related to JDBC Transaction.(java.sql.Connection)

I am using DB2 for z/OS.

As per the documentation, commit() or rollback() on Connection instance should throw SQLException if the Connection is under auto-commit mode. I have tried to test this, I do not get the exception.
Is it vendor- dependent ?

public static void main(String[] args) throws ClassNotFoundException,
			SQLException, InterruptedException {

		Connection con = establishConnection();
		System.out.println(con.getAutoCommit());
		

		Statement st = con.createStatement();
		setQuery();

//		con.setAutoCommit(false);
		int rows = st.executeUpdate(sql);
		System.out.println("rows updated: " + rows);
//		st.executeUpdate(sql);
//		st.executeUpdate(sql);
//		con.setAutoCommit(true);

		// rs = st.executeQuery(sql);
		// showResultSet(rs);

		con.rollback();
		
		con.commit();
	}

	private static void setQuery() {
		sql = "Update JavaTest set ID = ID + 1 ";
	}

I get the below output.

true
rows updated: 3

[Sibendu Dey]

Well the javadoc states the conditions under which the method will be called in addition the reason which is responsible for throwing SQLException

[Risha Rommi]

I am learning java thanks sharing this post

[Vinay Kumar T M]

OCP test do have this question in scope. It says, SQLException will be thrown if we try to commit or rollback when the connection is in auto-commit mode. I could not re create this scenario.

even some of the sample questions says, SQLException will be thrown.

To my understanding, it should throw SQLException. is it wrong ?

[Sibendu Dey]

It will be thrown when an database access error happens. Try performing a database operation which is not valid like inserting some data into a non-existent column. I guess you should get a SQLException.

[Vinay Kumar T M]

Try performing a database operation which is not valid like inserting some data into a non-existent column. I guess you should get a SQLException.

Thats the purpose of SQLException right ?. ofcourse, it should throw if we try to do invalid things. My question is not about doing invalid things. It is about the behaviour which is contradicting the oracle documentation. I might be very much , wrong...

So please help me understand.