But where its breaking existing features people rely on. Maybe a toggle needs
adding, where default allows old behaviours so that users dont get shock
behaviour changes. Sent from my Samsung Galaxy smartphone.
-------- Original message --------From: Clebert Suconic
<[email protected]> Date: 26/05/2019 17:53 (GMT+00:00) To:
[email protected] Subject: Re: Artemis 2.7.0 Cluster Redistribution Issue
To what is worth. We had a few AMQP purist developers complaining about
reencoding messages. And quite a few users about not working as
theyexpected.On Sun, May 26, 2019 at 1:53 AM
michael.andre.pearce<[email protected]> wrote:> Seems that
change is causing a number of issues. Someone flagged> transformer, also if
message is paged flags set are not preserved either> after depaging.Sent from
my Samsung Galaxy smartphone.> -------- Original message --------From: Clebert
Suconic <> [email protected]> Date: 26/05/2019 05:18 (GMT+00:00) To:>
[email protected] Subject: Re: Artemis 2.7.0 Cluster> Redistribution
Issue Can I get a version of your test working.The best way> would be in a fork
on your GitHub. I can take a look earlynext week.On Sat,> May 25, 2019 at 9:52
AM ldebello <[email protected]> wrote:> Hi,>>> After some debugging +
going back in commits the issue start happening>> after> this commit>>>>
https://github.com/apache/activemq-artemis/commit/6a64f4e7a270f83c735200d6ef29561ef4927535#diff-4a5cefc3ba360bce9985ad42fc0c2231R698>>>
I am assuming the redistribution is not "encoding" or updating the message>>
to multicast because the buffer is already valid and in previous version>>
reencode all the time so the message was ok>>>> --> Sent from:>>
http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html>--> Clebert
Suconic-- Clebert Suconic
