I'm facing some problems with the JDBC connection commit.
I'm using an Oracle8i client and server.
The jdbc library is classes12.jar
My application uses eclipse3.1 as an IDE and the jdk version is
jdk1.5.0_01
The flow of logic is such that I acquire 2 to 3 connections to my
database repository. On each of these connections some update/insert
statements
are executed (through jdbc PrepareStatement->executeUpdate())
After the update statements I issue a connection.commit() on each of
the connections where update statements are fired.
I have noticed sometimes that although connection.commit has been
issued, my DB does not have any data.
If anyone has any clue to this please let me know.
Re: Jdbc connection pooling without app/J2ee server ... > If using Jdbc outside of an application/J2ee server with the Microsoft ... Some drivers will offer an internal pooling feature,... useful for long-running applications that use lots of connections,... then pooling in the driver won't be able to help. ... (microsoft.public.sqlserver.jdbcdriver)
Re: Microsoft JDBC driver support connection pooling out of the box ... > If using Jdbc outside of an application/J2ee server with the Microsoft ... useful for long-running applications that use lots of connections,...pooling won't help. ... (microsoft.public.sqlserver.jdbcdriver)
jdbc commit issue ... I'm facing some problems with the JDBC connection commit.... I'm using an Oracle8i client and server.... The flow of logic is such that I acquire 2 to 3 connections to my ... the connections where update statements are fired. ... (comp.lang.java.databases)
jdbc commit issue ... I'm facing some problems with the JDBC connection commit.... I'm using an Oracle8i client and server.... The flow of logic is such that I acquire 2 to 3 connections to my ... the connections where update statements are fired. ... (comp.lang.java.databases)
