You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2014/12/16 21:53:13 UTC

[jira] [Updated] (AMQNET-495) Error in tight marshal handling of compacted long values reads leads to unmatched ack errors etc.

     [ https://issues.apache.org/jira/browse/AMQNET-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish updated AMQNET-495:
--------------------------------
    Fix Version/s: 1.6.5

> Error in tight marshal handling of compacted long values reads leads to unmatched ack errors etc.
> -------------------------------------------------------------------------------------------------
>
>                 Key: AMQNET-495
>                 URL: https://issues.apache.org/jira/browse/AMQNET-495
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ
>    Affects Versions: 1.6.4, 1.7.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Critical
>             Fix For: 1.7.0, 1.6.5
>
>
> The unmarshal code that deals with reading in tight marshaled long values that have been compacted to a less than eight bytes incorrectly reads these values as signed instead of unsigned as it should leading to incorrect data in unmarshalled objects.
> This can manifest when a message is received with a MessageId that has a producer sequence ID value greater than the max signed value of an int or short.  The Ack to the broker would contained an unknown message ID and lead to an error.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)