-
Notifications
You must be signed in to change notification settings - Fork 314
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.
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
fix(data.service): correctly stopping reconnection thread #5058
Merged
mattdibi
merged 1 commit into
eclipse-kura:develop
from
sfiorani:scheduled-connection-interval-fix
Dec 14, 2023
Merged
fix(data.service): correctly stopping reconnection thread #5058
mattdibi
merged 1 commit into
eclipse-kura:develop
from
sfiorani:scheduled-connection-interval-fix
Dec 14, 2023
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
Signed-off-by: SimoneFiorani <[email protected]>
mattdibi
approved these changes
Dec 13, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was the best review I ever did 😭
@sfiorani BTW does this spawn from a failed QA test? If so, can you review the test to comply with the modification added into this PR? |
Tested on RPi 64bit, all good
|
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.
This PR fixes a problem related to the management of the reconnection executor created by enabling the Connection Schedule option in the Data Service section of the Cloud Connections tab.
Before this change, when an update of the section was performed, no one stopped the reconnection executor, so the CloudConnection continously tried to reconnect with the old parameters, and could happen that the scheduled connections overlap, making the general behaviour not coherent with the expected one.
Related Issue:
Description of the solution adopted: This PR adds the correct stopping of the executor, which is then correctly update, so the next scheduled connections are coherent with the CRON expression set in the related option.
Screenshots:
Manual Tests:
Connect Auto-on-startup
option, enable theScheduled Connection
of DataService tab under CloudConnections with a CRON expression0/30 0/1 * 1/1 * ? *
and Apply.Message Store Provider Service PID
and changed it to a fake onefake.pid
and Apply."Reconnect task running. Stopping it"
Any side note on the changes made: