commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 8620] - Closed Connection Exception on setAutoCommit
Date Mon, 29 Apr 2002 17:30:31 GMT
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





------- Additional Comments From dan@wellogic.com  2002-04-29 17:30 -------
I am definitely calling close() on the connection to return it to the pool, I 
don't know how else to return it, since the connection is not pool-aware in 
any way.  According to the JavaDocs on PoolableConnection, I believe this is 
what I'm supposed to do:

A delegating connection that, rather than closing the underlying connection, 
returns itself to an ObjectPool when closed.

Perhaps PoolableConnection should check to make sure the connection is not 
closed before returning?

Of course, this still doesn't really answer the question of why is the 
connection closed, huh?

Anyway, I've attached a hacked together test.  Please excuse the sloppiness, I 
had to combine a half dozen classes to get it into one file.  You'll need to 
provide a SQL command on line 47, and change the connection url on line 189.

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message