[
https://issues.apache.org/jira/browse/ARTEMIS-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17442357#comment-17442357
]
Gary Tully commented on ARTEMIS-3173:
-------------------------------------
[~haanhvu] great news!
peek at:
[https://github.com/apache/activemq-artemis/blob/main/artemis-server/src/main/java/org/apache/activemq/artemis/core/management/impl/QueueControlImpl.java#L1577]
ideally there would be an api : queue.browserIterator(int startIndex) that
would 'jump' to the required place. I raised this without looking into it too
much but that is that start point... see how that is currently implemented and
see if there is a good way to initialise the start point of the iterator.
A little test that does the browse page view on messages that are paged would
be a good start point to be able to compare the responsiveness of getting the
100th page when we start at 0 or 100*pageSize.
> Queue control browse message in paged mode should not start from the
> beginning each time
> ----------------------------------------------------------------------------------------
>
> Key: ARTEMIS-3173
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3173
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: JMX
> Affects Versions: 2.17.0
> Reporter: Gary Tully
> Priority: Minor
>
> The implementation of the paged browser creates a browser iterator and
> searches from the start for each page contents. It wold be better if it was
> possible to jump right in. Especially when messages are not in memory, ie:
> address limit has caused paging.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
