[
https://issues.apache.org/jira/browse/ARTEMIS-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17249086#comment-17249086
]
ASF subversion and git services commented on ARTEMIS-3027:
----------------------------------------------------------
Commit 63a3bcbe3281b2f6efb29a708396bb93a5aa574f in activemq-artemis's branch
refs/heads/master from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=63a3bcb ]
ARTEMIS-3027 Fixing Redistribution of Large Messages after expiration fix
This is fixing AmqpLargeMessageRedistributionTes and
AMQPLargeMessageOverCoreBridgeTest after last commit on this issue.
> AMQP Expiration should be persisted on the journal
> --------------------------------------------------
>
> Key: ARTEMIS-3027
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3027
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Clebert Suconic
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Expiration calculation should be stored on as part of the journal in AMQP.
> if you set TTL, when you reboot the server the calculation would be
> re-applied instead of using the previous value.
> The broker should store the value instead of re-computing.
> There are other scenarios where this would be an issue as well, like
> appliedDelay from address settings.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
