Message:
The following issue has been resolved as FIXED.
Resolver: Daniel John Debrunner
Date: Tue, 5 Oct 2004 1:28 PM
Fixed by Committed revision 53822.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/DERBY-30
Here is an overview of the issue:
---------------------------------------------------------------------
Key: DERBY-30
Summary: Connection.close() method inconsistently throws exception on
closed connection
Type: Bug
Status: Resolved
Priority: Minor
Resolution: FIXED
Project: Derby
Components:
JDBC
Fix Fors:
10.0.2.0
Versions:
10.0.2.0
Assignee: Daniel John Debrunner
Reporter: Daniel John Debrunner
Created: Sat, 2 Oct 2004 7:17 PM
Updated: Tue, 5 Oct 2004 1:28 PM
Description:
JDBC 3.0 Javadoc for java.sql.Connection.close() states
"Calling the method close on a Connection object that is already closed is a
no-op."
In Derby embedded calling close on a closed connection from the DriverManager
or EmbeddedDataSource incorrectly throws XJ012.
Calling close on a closed connection from a ConnectionPoolDataSource or
XADataSource for Derby correctly returns correctly (no-op).
Similar issue for Statement.close() - needs to be a no-op on a closed
Statement/PreparedStatement/CallableStatement
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
