activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Rasmussen (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AMQ-4372) WebConsole throw Java Heap Space when browse a queue with more than 100 elements
Date Mon, 22 Apr 2013 10:05:16 GMT

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

Simon Rasmussen edited comment on AMQ-4372 at 4/22/13 10:03 AM:
----------------------------------------------------------------

I can confirm the issue:

OS: Windows 7
AMQ: 5.8.0

It occurs when I try to browse a queue using a tools such as ActiveMQBrowser which indicates
that it is a general issue.
                
      was (Author: smox):
    I can confirm the issue:

OS: Windows 7
AMQ: 5.8.0

I occurs when I try to browse a queue using a tools such as ActiveMQBrowser which indicates
that it is a general issue.
                  
> 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

Mime
View raw message