[
https://issues.apache.org/jira/browse/ARTEMIS-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-4768.
------------------------------------
> Property _AMQ_SCHED_DELIVERY lost from Scheduled Persistent Message after
> broker restart
> ----------------------------------------------------------------------------------------
>
> Key: ARTEMIS-4768
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4768
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.19.1, 2.33.0
> Reporter: Ajay P
> Assignee: Justin Bertram
> Priority: Major
> Fix For: 2.34.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Im seeing something peculiar related to messages with Scheduled Delivery on
> artemis 2.33.0 and a few prev versions too.
> We transmit persistent messages for scheduled delivery with the property
> _AMQ_SCHED_DELIVERY set to the time. There is a use case for being able to
> browse these queues for scheduled messages and remove them if they need to be
> canceled before delivery. This works fine and when browsing the queue using
> listScheduledMessages, all properties on said message are visible. We use
> this to show a list of scheduled messages that will be transmitted in the
> future.
> However, if the broker is restarted, then the message does not have that
> _AMQ_SCHED_DELIVERY property set anymore. The broker still delivers the
> message on the scheduled time but while browsing through the queue messages
> that specific property is not on the message.
>
> Here is a link to a fork with a test case checked in.
> [https://github.com/aahrimaan/activemq-scheduled-messages-issue]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
