This repository has been archived by the owner on Nov 4, 2024. It is now read-only.
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.
Thread interrupt was being called upon database unavailability (as in galasa-dev/projectmanagement#570).
Explanation of the problem has been added in that tagged issue.
I have added a check to see if the
CompletableFuture
completes with an exception (this exception signals database unavailability, at least in reference to the tagged issue), and enforce a re-try if there is an exception (with a max number of retries).The multi-catch has also been split up so that
InterruptedException
andExecutionException
are treated differently.Closes galasa-dev/projectmanagement#570 when combined with a PR being raised in galasa-dev/framework that references the same issue.
Signed-off-by: Matthew Chivers matthewchivers@outlook.com