You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2013/07/11 20:23:48 UTC

[jira] [Commented] (AMQ-4595) QueueBrowser hangs when browsing large queues

    [ https://issues.apache.org/jira/browse/AMQ-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706068#comment-13706068 ] 

Timothy Bish commented on AMQ-4595:
-----------------------------------

Since the Queue depth exceeds the maxAuditDepth on the Queue the browse runs into the problem similar to AMQ-4487 which can be resolved by setting maxAuditDepth to some higher value.  Then you must also take into account that the browse will end when the memory limit is reached so you would need to configure a very large limit for this test case to get all 10,000 messages since they have a larger payload.  The updated test case shows how its done. 
                
> 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