[
https://issues.apache.org/jira/browse/ARTEMIS-5032?focusedWorklogId=933415&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-933415
]
ASF GitHub Bot logged work on ARTEMIS-5032:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 05/Sep/24 15:29
Start Date: 05/Sep/24 15:29
Worklog Time Spent: 10m
Work Description: tabish121 opened a new pull request, #5216:
URL: https://github.com/apache/activemq-artemis/pull/5216
Ensure that on server restart the original priority value assigned to an
AMQP message is used when dispatching durable messages from the store. The AMQP
Header section is scanned if present and the priority value is recovered in an
efficient manner.
Issue Time Tracking
-------------------
Worklog Id: (was: 933415)
Remaining Estimate: 0h
Time Spent: 10m
> Message priority not honored for persisted AMQP messages after server
> restarted
> -------------------------------------------------------------------------------
>
> Key: ARTEMIS-5032
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5032
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.37.0
> Reporter: Timothy A. Bish
> Assignee: Timothy A. Bish
> Priority: Minor
> Fix For: 2.38.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Messages sent with a non-default priority level that are persisted and later
> recovered after a server restart do not get delivered according to their
> original message priority but are all treated as having the default priority
> value (priority 4).
--
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
