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

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

                Author: ASF GitHub Bot
            Created on: 06/Feb/26 14:43
            Start Date: 06/Feb/26 14:43
    Worklog Time Spent: 10m 
      Work Description: AntonRoskvist commented on PR #5593:
URL: https://github.com/apache/artemis/pull/5593#issuecomment-3860853525

   @jbertram 
   
   This should be looking better.
   
   Wish I could say the full test suite passes with these changes but I'm 
having some issues running the suite in it's entirety at the moment (against 
both main and this PR) where many tests are failing intermittently (mostly 
around AMQP and clustering/bridging). It's probably something on my end but I 
have yet to figure out what... in any case, it's making proper validation of 
the changes difficult.
   
   I will look into that during next week but until then, from all I've been 
able to test and validate, this is looking good.




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

    Worklog Id:     (was: 1003912)
    Time Spent: 1h 20m  (was: 1h 10m)

> 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
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 20m
>  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