[
https://issues.apache.org/jira/browse/AMQ-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706779#comment-13706779
]
Torsten Mielke commented on AMQ-4595:
-------------------------------------
Hi Tim,
Do you mind explaining a bit more why maxAuditDepth needs to be raised in order
to browse a higher number of messages?
Also, I barely found any documentation on this property. Can we get it added to
http://activemq.apache.org/per-destination-policies.html?
Would the current behavior (when not setting maxAuditDepth) not rather be a
bug? From a client's point of view should a queue browser not be used like an
ordinary consumer and not require any broker side config changes?
I am concerned that no ActiveMQ user will think of raising maxAuditDepth in
order to browse more than the default 400 messages. This does not seem
intuitive.
And finally I want to add that you also need to use version 5.9-SNAPSHOT as
even the updated test case does not work with 5.8.0. I presume due to the fix
that went in for AMQ-4487?
> QueueBrowser hangs when browsing large queues
> ---------------------------------------------
>
> Key: AMQ-4595
> URL: https://issues.apache.org/jira/browse/AMQ-4595
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.8.0
> Environment: All
> Reporter: Nicholas Rahn
> Priority: Critical
> Labels: QueueBrowser
> Attachments: AMQ4595Test.java, AMQ580BrowsingBug.java,
> amq-test-20130621T155120.log
>
>
> When trying to browse a queue with a QueueBrowser, the browsing will hang and
> never complete. This appears to happen only with "a lot" of message in the
> queue. 1000 messages works correctly, but 10000 hangs.
> I have attached a unit test that exhibits the problem. Change the
> "messageToSend" variable in the test method to see the difference between
> small queue size and large queue size.
> I've attached the unit test code as well as the output from one of the runs
> with 10000 messages.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
