fix: send NACK after storing oversized HL7 message #2646 #2650
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
Contributor
Shreeja-dev
commented
Jan 30, 2026
Shreeja-dev
commented
- Send NACK for oversized messages
- Set TCP_MAX_MESSAGE_SIZE_BYTES default to 52428800 (50 MB)
- Set TCP_READ_TIMEOUT_SECONDS default to 180 seconds
added 2 commits
January 30, 2026 17:18
- Send NACK for oversized messages - Set TCP_MAX_MESSAGE_SIZE_BYTES default to 52428800 (50 MB) - Set TCP_READ_TIMEOUT_SECONDS default to 180 seconds
raphaelvp
approved these changes
Jan 30, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.