You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by bu...@apache.org on 2004/11/30 04:33:28 UTC

DO NOT REPLY [Bug 32441] New: - [DBCP] SQLException When PoolablePreparedStatement Already Closed

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32441>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32441

           Summary: [DBCP] SQLException When PoolablePreparedStatement
                    Already Closed
           Product: Commons
           Version: 1.2 Final
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P2
         Component: Dbcp
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: apache_bugzilla@zwiers.ca


When closing an already closed
org.apache.commons.dbcp.PoolablePreparedStatement, a SQLException is thrown when
the isClosed() method returns true.

This seems to violate the contract of java.sql.Statement (super interface of
implemented PreparedStatement) whose javadoc reads " Calling the method close on
a Statement  object that is already closed has no effect." 

Work around exists -- when ever closing a statement, also null out.  Then,
before closing, check that it's non-null.

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

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