You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Lorenz Quack (JIRA)" <ji...@apache.org> on 2017/06/01 10:51:04 UTC
[jira] [Closed] (QPID-7766) [Java Broker] [Derby Store] Unsigned
byte type should be used when reading stored message metada type
[ https://issues.apache.org/jira/browse/QPID-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lorenz Quack closed QPID-7766.
------------------------------
> [Java Broker] [Derby Store] Unsigned byte type should be used when reading stored message metada type
> -----------------------------------------------------------------------------------------------------
>
> Key: QPID-7766
> URL: https://issues.apache.org/jira/browse/QPID-7766
> Project: Qpid
> Issue Type: Bug
> Affects Versions: qpid-java-6.1, qpid-java-6.1.1, qpid-java-6.1.2
> Reporter: Alex Rudyy
> Assignee: Alex Rudyy
> Fix For: qpid-java-broker-7.0.0, qpid-java-6.1.3
>
>
> Meta data type is read into variable of type {{byte}} in current implementation of {{AbstractJDBCMessageStore#getMetaData}}. As result, the type values above 127 are read as negative values causing {{ArrayIndexOutOfBoundsException}} on invocation of {{MessageMetaDataTypeRegistry#fromOrdinal}}. Unsigned byte type should be used when reading stored message meatada type.
> This defect prevents the recovery of "flowed to disk" messages published with REST API or AMQP management, because metadata type for such messages is 255 which is turned into -1 when signed byte is used.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org