Jeff,
For iBatis app with SimpleDatasource & DBCP, the transaction is getting
rolled back. (are u running a test case or something)
With Glassfish there is neither a commit or rollback being issued, which is
the problem, since AutoCommit is set to false.
With straight JDBC, i believe you are using
Hi all,
I am connecting to the oracle database via Ibatis and getting
the java.sql.SQLException: Invalid Oracle-URL
I am using oracle client installation (for oracle 10g-10.2.0.1) /oracle
thick driver as jdbc-driver and have
If I connect the same database with the same url from java directl
Try jdbc:oracle:oci:@your_hostname:1521:your_sid
-Richard
Sent from my iPhone
On Apr 17, 2009, at 3:16 AM, pitaeva wrote:
Hi all,
I am connecting to the oracle database via Ibatis and getting
the java.sql.SQLException: Invalid Oracle-URL
I am using oracle client installation (for oracle 1
Jeff,
The autocommit is not the issue here - sorry to have confused you by
raising that, i wanted to highlight another point, but lets ignore that to
keep it simple.
The issue is that with Glassfish, the commit or rollback is not coming to
the JDBC driver, whereas with Simple/DBCP there is a rol
I am not sure if you have this figured out already, but I use Websphere and
DB2, and a couple years ago we were trying to understand if a read
transaction needed to be committed. Apparently it does for the connection
to be returned to the connection pool and Websphere does it implicitly as we
late
THANKS! . I just had to add the "commitRequired=true" option on the
iBATIS sqlMapconfig.xmlSo it looks like:
As you mention, apparently DB2 requires commits on reads and the other
connection pool implementations (non-GlassFish) take care of this for you.
Also thanks to Mario B
