DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=31811>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31811 [DBCP] per-user pooling with Oracle driver and default isolation settings Summary: [DBCP] per-user pooling with Oracle driver and default isolation settings Product: Commons Version: 1.2 Final Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Dbcp AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] 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 Bug 25001 PATCH: Oracle 9i and default isolation settings --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
