[ 
https://issues.apache.org/jira/browse/ARTEMIS-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17718553#comment-17718553
 ] 

ASF subversion and git services commented on ARTEMIS-4268:
----------------------------------------------------------

Commit 589157ca5f7b07528e09d207282cb00a7796db67 in activemq-artemis's branch 
refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=589157ca5f ]

ARTEMIS-4268 AMQPMessage copy constructor shouldn't copy all message annotations

During redistribution, we should not copy all message annotations.

In particular we should not copy any of the x-opt-ORIG annotations used on DLQ 
and other copies.

this was broken after f632e8104bbdae1fbf3658fec47e180784e957da (ARTEMIS-3833 
Preserve JMSCorrelationID of distributed AMQP large messages)

The change preserved too much, and as a result of that 
AmqpLargeMessageRedistributionTest::testSendMessageToBroker0GetFromBroker2 is 
intermittently failing.

There is no test in this commit as this is fixing 
AmqpLargeMessageRedistributionTest


> AMQPMessage copy constructor shouldn't copy all message annotations
> -------------------------------------------------------------------
>
>                 Key: ARTEMIS-4268
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4268
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Clebert Suconic
>            Priority: Major
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> During redistribution, we should not copy all message annotations.
> In particular we should not copy any of the x-opt-ORIG annotations used on 
> DLQ and other copies. 
> this was broken after f632e8104bbdae1fbf3658fec47e180784e957da (ARTEMIS-3833 
> Preserve JMSCorrelationID of distributed AMQP large messages)
> The change preserved too much, and as a result of that 
> AmqpLargeMessageRedistributionTest::testSendMessageToBroker0GetFromBroker2 is 
> intermittently failing.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to