Issues with conn.setAutoCommit(false) ?
MarkM at relais-intl.com
Mon Jun 26 09:14:28 EDT 2000
Everything is exactly the same for both drivers. There is an if/else if
statement at the beginning of my LoginServlet that selects which driver to
use, then after that the only differences in the code for the two are in the
select statements with joins in them (just different syntax for Oracle/SQL
This morning I decided to try adding a call to commit() a few lines before
the "hang" was occuring, and it worked. It would seem that there is a
maximum amount of data that can build up before calling commit().
From: Bob Kline [mailto:bkline at rksystems.com]
Sent: Sunday, June 25, 2000 3:04 PM
To: TDS Development Group
Subject: [freetds] Re: Issues with conn.setAutoCommit(false) ?
On Fri, 23 Jun 2000, Mark MacRae wrote:
> I seem to be having trouble with the JDBC driver when I turn off
> auto commit. During one of my stmt.executeUpdate(), everything just
> I've run the exact same code with no problems through the Oracle
> thin driver, so I'm assuming is has to do with something either
> unimplemented in FreeTDS or just a bug.
What variables (other than the DBMS, which is presumably not the same),
are different between the Oracle run and the freeTDS run? Same JVM?
Same version of JDBC? Same client platform? What happens if you try a
different JVM? What happens if you re-arrange the sequence of SQL
statements (for example, instead of submitting them all from the same
process, breaking them into smaller groups and running separate
processes for each group)? What happens if you submit the same sequence
of SQL statements using a different client (for example, isql) but with
the same approach to transaction handling?
You are currently subscribed to freetds as: MarkM at relais-intl.com
To unsubscribe, forward this message to
More information about the FreeTDS