You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2002/04/29 15:57:04 UTC
DO NOT REPLY [Bug 8620] New: -
Closed Connection Exception on setAutoCommit
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8620>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8620
Closed Connection Exception on setAutoCommit
Summary: Closed Connection Exception on setAutoCommit
Product: Commons
Version: unspecified
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Normal
Priority: Other
Component: Dbcp
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: dan@wellogic.com
After roughly a half dozen successful uses, I throw a SQLException when doing
a setAutoCommit(false) on a connection returned from DBCP. I have tested this
with both Microsoft SQL Server 2000 using JSQLConnect and Oracle 8.1.7.0.0
using the Oracle provided thin drivers. My application makes heavy use of
transactions, if that could be part of the problem. If I set both validations
to be true, then it always rejects the connection on return to the pool, and
everything works fine (except that I'm not reusing connections, of course).
If I don't do validation, then I get this exception after a few successful
connections:
java.sql.SQLException: Closed Connection
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:180)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:222)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:285)
at oracle.jdbc.driver.OracleConnection.setAutoCommit
(OracleConnection.java:991)
at org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(Unknown
Source)
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>