QPIDJMS-617: BytesMessage increments the read pointer position on MessageFormatException #56
+28
−0
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
…sageFormatException
dakirily
force-pushed
the
QPIDJMS-617
branch
from
7ae7262 to
a0a8fae
Compare
tabish121
reviewed
Jan 6, 2026
| try { | ||
| this.dataIn.reset(); | ||
| } catch (IOException ignored) | ||
| { |
Contributor
There was a problem hiding this comment.
Formatting here is incorrect and should match the rest of the codebase
…sageFormatException (fixed formatting)
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.
This PR addresses JIRA QPIDJMS-617, resetting the read pointer position in JmsBytesMessage#readUTF() in case of a MessageFormatException