[DERBY-30] Connection.close() method inconsistently throws exception on closed connection

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.0.2.0
• Fix Version/s: 10.0.2.0
• Component/s: JDBC
• Assignee: Daniel John Debrunner
• Reporter: Daniel John Debrunner
• Created: 03/Oct/04 02:17
• Updated: 04/Jun/05 22:34
• Resolved: 05/Oct/04 20:28

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