fix: prevent concurrent result sets for a statement #39
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MikeDombo
previously approved these changes
Dec 4, 2023
jcosentino11
force-pushed
the
get-sync
branch
from
477770c
to
c99b808
Compare
|
Unit Tests Coverage Report
Minimum allowed coverage is Generated by 🐒 cobertura-action against c99b808 |
vabhasin
approved these changes
Dec 4, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes:
Since moving to cached connections, we've began seeing
java.sql.SQLException: ResultSet already requestedfailures in UATs. This change synchronizesgetSpoolMessageByIdandgetAllSpoolMessageIdsto ensure there's one result set being operated on for a given statementBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.