You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/05/03 13:19:04 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15994832#comment-15994832 ]
ASF subversion and git services commented on QPID-7766:
-------------------------------------------------------
Commit 593d157782d0080ecce2a744c649a050f969738e in qpid-broker-j's branch refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=593d157 ]
QPID-7766: [Java Broker] [Derby Store] Unsigned byte type should be used when reading stored message metada type
> [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
> 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 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