db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From derby-...@db.apache.org
Subject [jira] Updated: (DERBY-30) Connection.close() method inconsistently throws exception on closed connection
Date Mon, 04 Oct 2004 15:55:32 GMT
The following issue has been updated:

    Updater: Daniel John Debrunner (mailto:djd@debrunners.com)
       Date: Mon, 4 Oct 2004 8:54 AM
    Changes:
             description changed from 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).
 to 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

    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/DERBY-30?page=history

---------------------------------------------------------------------
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: Open
   Priority: Minor

    Project: Derby
 Components: 
             JDBC
   Versions:
             10.0.2.0

   Assignee: Daniel John Debrunner
   Reporter: Daniel John Debrunner

    Created: Sat, 2 Oct 2004 7:17 PM
    Updated: Mon, 4 Oct 2004 8:54 AM

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


Mime
View raw message