commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark W (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DBCP-413) Closing a Connection does not close Statement objects created on that connection, by way of the close() method.
Date Wed, 09 Apr 2014 21:27:14 GMT

    [ https://issues.apache.org/jira/browse/DBCP-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13964681#comment-13964681
] 

Mark W commented on DBCP-413:
-----------------------------

it may be a driver issues, but I didn't know which it was, DBCP or our drivers. Thought I
would start here. I doubt I will be able to upgrade DBCP. Do you know of a way for me to verify
that it is the MS drivers?

> Closing a Connection does not close Statement objects created on that connection, by
way of the close() method.
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: DBCP-413
>                 URL: https://issues.apache.org/jira/browse/DBCP-413
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.4
>            Reporter: Mark W
>            Priority: Minor
>
> While using the MS SQL 2012 jdbc drivers with dbcp, I noticed that if you create a connection,
then create a preparedStatement from that connection, and close the connection object, PreparedStatement.isClosed()
will return false, but you will get a SQLException stating the statement has been closed if
you attempt to call any of the set or execute methods.
> From the JDBC spec:
> Connection.close
> An application calls the method Connection.close() to indicate that it has finished using
a connection. All Statement objects created from a given Connection object will be closed
when the close method for the Connection object is called.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message