[ 
https://issues.apache.org/jira/browse/ARTEMIS-5376?focusedWorklogId=1007215&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1007215
 ]

ASF GitHub Bot logged work on ARTEMIS-5376:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 25/Feb/26 18:10
            Start Date: 25/Feb/26 18:10
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic opened a new pull request, #6251:
URL: https://github.com/apache/artemis/pull/6251

   (no comment)




Issue Time Tracking
-------------------

    Worklog Id:     (was: 1007215)
    Time Spent: 2.5h  (was: 2h 20m)

> 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: 2.5h
>  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]

Reply via email to