[
https://issues.apache.org/jira/browse/ARTEMIS-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18061757#comment-18061757
]
ASF subversion and git services commented on ARTEMIS-5376:
----------------------------------------------------------
Commit e9dbc111f0c7ff4ce8941cb18bcae5edb07ae43a in artemis's branch
refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=artemis.git;h=e9dbc111f0 ]
ARTEMIS-5376 Using iterQueue on deleteReferences
> Include all messages in queue management operations
> ---------------------------------------------------
>
> Key: ARTEMIS-5376
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5376
> Project: Artemis
> Issue Type: Improvement
> Reporter: Anton Roskvist
> Assignee: Anton Roskvist
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.52.0
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Currently, some queue management operations act on all messages (including
> paged and scheduled messages) and some don't. Some operations use their own
> iterator logic (internally) and some use a common method.
> This change aims to improve this by adding some functionality into the
> 'QueueIterateAction' class and then have additional management operations use
> it (so that their behavior is consistent with regards to what messages they
> target and how)
> As of now I have left expire and delete reference/references out as I wasn't
> 100% sure it wont have any adverse effects. If desired, they should be
> trivial to add as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
