Skip to content

Fixed intermittent null prepared statement handle #1886

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 4, 2022
Merged

Fixed intermittent null prepared statement handle #1886

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion src/main/java/com/microsoft/sqlserver/jdbc/SQLServerPreparedStatement.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2910,7 +2910,12 @@ final void doExecutePreparedStatementBatch(PrepStmtBatchExecCmd batchCommand) th
if (!getNextResult(true))
return;

if (isSpPrepareExecuted) {
// If sp_prepare was executed, but a handle doesn't exist that means
// the TDS response for sp_prepare has not been processed yet. Rather, it means
// that another result was processed from a sp_execute query instead. Therefore, we
// skip the if-block below and continue until the handle is set from the processed
// sp_prepare TDS response.
if (isSpPrepareExecuted && hasPreparedStatementHandle()) {
isSpPrepareExecuted = false;
resetForReexecute();
tdsWriter = batchCommand.startRequest(TDS.PKT_RPC);
Expand Down