[
https://issues.apache.org/jira/browse/AMQ-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reopened AMQ-4181:
-----------------------------
think we need a way to make this change configurable based on the existing
maxBrowsePageSize. It is now obsolete, but I think using a value of -1 to mean
ignore the page limit and use all available memory could make sense. In other
words, to remove the browsePageLimit use a value of -1 and when it is specified
> 0 it is the hard limit.
This means that really large depths can be bounded in a browse. consider a
queue with 1m messages and lots of broker memory... our browser will fall over.
> JMS queue browser returns only page size number of messages
> -----------------------------------------------------------
>
> Key: AMQ-4181
> URL: https://issues.apache.org/jira/browse/AMQ-4181
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.7.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.8.0, 5.10.0
>
>
> When the number of messages in the queue is larger than set page size, the
> jms queue browser will get one page size of messages (200 by default).
> Ideally we'd want to send all the messages or at least until we reach the
> memory limit set for the queue/broker.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
