You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe there is a statement leak in SQLServerPreparedStatement.getMetaData(). If no result set is present #getMetaData() calls #buildExecuteMetaData() which in tern creates and executes a statement and returns a result set. #close() on this result set and statement is never called because the caller of #getMetaData() only sees a ResultSetMetaData object which has no #close() method.
The following code can be used to reproduce the issue
The text was updated successfully, but these errors were encountered:
marschall
changed the title
Statement leak in com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.getMetaData()
Statement leak in SQLServerPreparedStatement.getMetaData()
May 20, 2017
I believe there is a statement leak in
SQLServerPreparedStatement.getMetaData()
. If no result set is present#getMetaData()
calls#buildExecuteMetaData()
which in tern creates and executes a statement and returns a result set.#close()
on this result set and statement is never called because the caller of#getMetaData()
only sees aResultSetMetaData
object which has no#close()
method.The following code can be used to reproduce the issue
The text was updated successfully, but these errors were encountered: