FIX for manager restart issue due to EAGAIN 0MQ error #333
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Fix for recently discovered issue of the manager process restarting during security network scans. The EAGAIN exception was raised and processed during receive operation, but since no data was actually received, the send (reply) operation also failed with the exception that was not processed, which caused the restart of the manager. The issue was fixed by separately processing EAGAIN exception and retrying the receive until the data is received.
Fixed
How Has This Been Tested?
No method to reproduce the issue in unit tests. The modified code was tested in on the workstation exposed to network scans.