You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Timothy A. Bish (Jira)" <ji...@apache.org> on 2026/01/06 22:39:00 UTC
[jira] [Resolved] (QPIDJMS-617) BytesMessage increments the read pointer position on MessageFormatException
[ https://issues.apache.org/jira/browse/QPIDJMS-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy A. Bish resolved QPIDJMS-617.
-------------------------------------
Fix Version/s: 1.16.0
Resolution: Fixed
> BytesMessage increments the read pointer position on MessageFormatException
> ---------------------------------------------------------------------------
>
> Key: QPIDJMS-617
> URL: https://issues.apache.org/jira/browse/QPIDJMS-617
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 2.9.0
> Reporter: Daniil Kirilyuk
> Priority: Minor
> Fix For: 2.10.0, 1.16.0
>
>
> Jakarta Messaging specification version 3.1 states in chapter [3.11.3|https://jakarta.ee/specifications/messaging/3.1/jakarta-messaging-spec-3.1#conversions-provided-by-streammessage-and-mapmessage]:
> "If a read method of StreamMessage or BytesMessage throws a MessageFormatException or NumberFormatException, the current position of the read pointer must not be incremented. A subsequent read must be capable of recovering from the exception by rereading the data as a different type".
> Currently JmsBytesMessage increments the read pointer position, making it impossible to reread the data after the exception.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org