issue #1300 TxManagerImpl.nextTxNumber(): Repeat attempt on racing condition #1343
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
JaCoCo code coverage report
|
…1200 error (racing cond.)
wajda
force-pushed
the
bugfix/spline-1300-arango-400
branch
from
6b3458a to
825c2a4
Compare
|
cerveada
approved these changes
Jul 2, 2024
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.
fixes #1300
The method
TxManagerImpl.nextTxNumber()is supposed to be acting in an increment-and-get fashion tolerating racing conditions. For that reason it should contain a loop to repeat attempts in case of a conflict.