[DBCP] per-user pooling with Oracle driver and default isolation settings

• Key: DBCP-20
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Major
• Assignee: Unassigned
• Reporter: Dirk Verbeeck
• Affects Version/s: 1.2

Environment

Operating System: All
Platform: All

Description

Issue reported by Chris Nappin on commons-dev 18 okt 2004
----------------------------------------------------------
I'm trying to configure per-user connection pooling with Tomcat, DBCP
and the Oracle 9i JDBC driver. A connection with default driver settings
seems to work, but when setting auto-commit to false I get errors. I've
tried DBCP 1.1 and 1.2.1 (with Pool 1.1 or 1.2).

This works fine, once (a read query using a new connection). However,
when DBCP tries to re-use a pooled connection, I get:
java.sql.SQLException: ORA-01453: SET TRANSACTION must be first
statement of transaction
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)

The bug I'm seeing seems very similar to the following, which was
resolved in DBCP 1.2.1:
Bugzilla COM-973
PATCH: Oracle 9i and default isolation settings