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

Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2019/01/18 02:21:07 UTC

[jira] [Closed] (ARTEMIS-2082) AMQP: Message corruption possible on redelivered message that have moved

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

clebert suconic closed ARTEMIS-2082.
------------------------------------

> AMQP: Message corruption possible on redelivered message that have moved
> ------------------------------------------------------------------------
>
>                 Key: ARTEMIS-2082
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2082
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: AMQP
>    Affects Versions: 2.6.3
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Major
>             Fix For: 2.6.4
>
>
> In some cases when a message moves from one Queue to another either by expiration or other policy defined reason the messages that are sent to clients on the new location of the message can become corrupted if the the client consumes but does not settle the message.  This can occur for instance with a transacted consumer that continually rolls back the message and then consumes it again.  The message eventually becomes corrupt as the broker's internal AMQPMessage object loses track of the location of various portions of the message data and re-encodes the header to add a delivery count etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)