activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicholas Rahn (JIRA)" <>
Subject [jira] [Commented] (AMQ-4595) QueueBrowser hangs when browsing large queues
Date Mon, 15 Jul 2013 08:10:50 GMT


Nicholas Rahn commented on AMQ-4595:

We make extensive use of the QueueBrowser in our application (our app is similar to the activemq
web console app where you can view all queues, connections, messages; and move messages between
any 2 queues). So having a solution that does not require us to change a queue's configuration
is important as we don't know queue names, message size or queue size before hand. 

I'm not all that familiar with the internals of AMQ, but in the old AMQ 4.0 series (we're
upgrading from that series, btw), we would not have memory issues unless you browsed a *very*
large queue (100000s messages). Upgrading the Queue Browser code would also benefit the activemq
web console app, as anyone using that will also be bitten by this bug.

> QueueBrowser hangs when browsing large queues
> ---------------------------------------------
>                 Key: AMQ-4595
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.8.0
>         Environment: All
>            Reporter: Nicholas Rahn
>            Priority: Critical
>              Labels: QueueBrowser
>         Attachments:,, 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

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:

View raw message