tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 46201] New: jdbc-pool : con.close() should no-op if already closed
Date Thu, 13 Nov 2008 17:34:10 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=46201

           Summary: jdbc-pool : con.close() should no-op if already closed
           Product: Tomcat 6
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina
        AssignedTo: dev@tomcat.apache.org
        ReportedBy: funkman@joedog.org


Connection con = datasource.getConnection();
con.close();
con.close();

The javadcos for close say:
Calling the method close on a Connection  object that is already closed is a
no-op. 


The current behavior is "Caught: java.sql.SQLException: Connection has already
been closed."


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message