[ http://issues.apache.org/jira/browse/DERBY-30?page=all ] Daniel John Debrunner closed DERBY-30: --------------------------------------
> Connection.close() method inconsistently throws exception on closed connection > ------------------------------------------------------------------------------ > > Key: DERBY-30 > URL: http://issues.apache.org/jira/browse/DERBY-30 > Project: Derby > Type: Bug > Components: JDBC > Versions: 10.0.2.0 > Reporter: Daniel John Debrunner > Assignee: Daniel John Debrunner > Priority: Minor > Fix For: 10.0.2.0 > > 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 -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
