Issue Details (XML | Word | Printable)

Key: DERBY-30
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Daniel John Debrunner
Reporter: Daniel John Debrunner
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Derby

Connection.close() method inconsistently throws exception on closed connection

Created: 03/Oct/04 02:17 AM   Updated: 04/Jun/05 10:34 PM
Return to search
Component/s: JDBC
Affects Version/s: 10.0.2.0
Fix Version/s: 10.0.2.0

Time Tracking:
Not Specified

Resolution Date: 05/Oct/04 08:28 PM


 Description  « Hide
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


 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Daniel John Debrunner made changes - 04/Oct/04 03:54 PM
Field Original Value New Value
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).
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
Daniel John Debrunner added a comment - 05/Oct/04 08:28 PM
Fixed by Committed revision 53822.

Daniel John Debrunner made changes - 05/Oct/04 08:28 PM
Resolution Fixed [ 1 ]
Status Open [ 1 ] Resolved [ 5 ]
Fix Version/s 10.0.2.0 [ 10920 ]
Daniel John Debrunner made changes - 04/Jun/05 10:34 PM
Status Resolved [ 5 ] Closed [ 6 ]