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 2020/12/10 01:08:00 UTC

[jira] [Created] (ARTEMIS-3026) Allow "reencoding" of application properties on AMQP Large Messages

Clebert Suconic created ARTEMIS-3026:
----------------------------------------

             Summary: Allow "reencoding" of application properties on AMQP Large Messages
                 Key: ARTEMIS-3026
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3026
             Project: ActiveMQ Artemis
          Issue Type: Bug
            Reporter: Clebert Suconic
            Assignee: Clebert Suconic


Currently if Diverts or other things call amqplargeMessage.reencode() this is a moot operation, and there's no way to re-encode the application Properties, Properties or anything in the LargeMessage.

 

It should be possible to allow replacing the application properties upon sending. 

 

We save the modified application properties anyways on the journal record. So, we should allow ProtonServerSenderContext to replace the original application properties by a new set if reencode() is called anywhere on the message.

 

There should be a flag that would be stored as part of the journal allowing the broker to know if the message was ever re-encoded.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)