[ https://issues.apache.org/jira/browse/AMQ-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655098#comment-13655098 ]
David Lloyd commented on AMQ-4372: ---------------------------------- Appear to have the same issue here, running ActiveMQ 5.8.0 on Java 1.7.x (Windows 7) - queues stored in SQL Server 2008 R2 Have also attempted to browse the queue with alternative queue browsers, using HermesJMS to browse a queue with 92 messages queued it retrieved over 500,000 messages from the queue before I told it to stop. It appears to get stuck in a loop and repeatedly retrieve the same 92 messages (which makes more sense to me that this runs the default browser out of heap space when a handful fewer messages are no problem). When replaying messaging into the queue from HermesJMS, even with 2000 messages in the queue the default browser loads them in under 2 seconds, we only seem to encounter this issue when the queue is populated from our application which is using the Apache NMS API. > WebConsole throw Java Heap Space when browse a queue with more than 100 > elements > -------------------------------------------------------------------------------- > > Key: AMQ-4372 > URL: https://issues.apache.org/jira/browse/AMQ-4372 > Project: ActiveMQ > Issue Type: Bug > Components: Broker > Affects Versions: 5.8.0 > Environment: Linux/Ubuntu > Reporter: Grégory OLIVER > Labels: web-console > Fix For: 5.9.0 > > > I have a standalone installation of activemq. > When I want to browse a queue with more than 100 elements, the console throw > a Java Heap Space, because he try to show all elements in the queue. > But when I have 40 elements, the page work well, and i can browse messages. > It should be interesting to paginate this page, to only show, for example, > the first 100 elements. > The page : > http://localhost:8161/admin/browse.jsp?JMSDestination=TestQueueOne > Added : > I have tested with the 5.7.0 version of activemq and this bug doesn't exist. -- 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