Archives of the TeradataForum

Message Posted: Mon, 08 Sep 2008 @ 15:13:09 GMT


	<Prev	Next>		<<First	<Prev	Next>	Last>>

Subj:		Re: JDBC autoCommit(false) question

From:		McCall, Glenn David

This question is related to Teradata JDBC Connection autoCommit() setting. In our application we have set autoCommit() to "false" to attain application driven transaction behavior.

Surprising though, I found that autoCommit set to false results in some extra commits getting fired which are definitely not from the application.

I've used autocommit false occasionally - mostly for testing it out.

I've not seen the behaviour you mention. So I can't help, but what have you tried so far?

For example:

You mention that you can see the extra commits in the "logs". Does it happen after anything specific, or is it seemingly at random? Is there any pattern to the extra commits?

Are you using a connection pool? Perhaps when you return the connection to the pool, the pool manager (or driver) forces a commit.

How are you committing? Are you using the commit method or submitting a "commit" query?

Are you using ANSI or Teradata mode? Have you tried the other one?

Have you tried updating the driver?

Can you narrow this problem done to a simple program that you can post?

I hope this gives you some food for thought.

Glenn Mc


	<Prev	Next>		<<First	<Prev	Next>	Last>>

Attachments

Library

Quick Reference