Fix not connected error in STOMP output #2423
Merged
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
kamil-certat
force-pushed
the
fix_not_connected_error
branch
from
412db76 to
1cd6eec
Compare
Sometimes the output bot gots disconnected, and stays so until restart or reload. This change adds a try to reconnect. It intentionally doesn't hide the error, but let's IntelMQ handle message retry.
kamil-certat
force-pushed
the
fix_not_connected_error
branch
from
1cd6eec to
a81572a
Compare
sebix
approved these changes
Nov 29, 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.
This PR depends on PR #2414 and handles connection errors in the output bot