[ 
https://issues.apache.org/jira/browse/AMQ-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John Stall updated AMQ-4419:
----------------------------

    Description: 
Use of QueueBrowser without destination memory limits causes AMQ to run out of 
heap space.  Retrieving QueueBrowser elements appears to ignore global 
MemoryUsage and default browsePageSize of 200.  Install default 5.8.0 binary 
distro.  Create 5000 persistent messages in queue and browse to see contents . 
Shutdown, and change the queue policy entry so that it doesn't limit the 
destination memory(remove memoryLimit="1mb").  Startup broker, and attempt to 
view the same 5000 entries.  This time the results will not be limited and the 
broker will run out of heap space.  Same occurs if using QueueBrowser 
programmatically.  Works in previous versions as results were limited by page 
size.

May be related to-

https://issues.apache.org/jira/browse/AMQ-4181?page=com.atlassian.jirafisheyeplugin:fisheye-issuepanel

  was:
Use of QueueBrowser without destination memory limits causes AMQ to crash.  It 
appears to ignore global MemoryUsage.  Install default 5.8.0 binary distro.  
Create 5000 messages in queue and browse to see contents . Shutdown, and change 
the queue policy entry so that it doesn't limit the memory(remove 
memoryLimit="1mb").  Startup broker, and attempt to view the same 5000 entries. 
 This time the results will not be limited and the broker will run out of heap 
space.  Same occurs if using QueueBrowser programmatically.  Works in previous 
versions as results were limited by page size.

May be related to-

https://issues.apache.org/jira/browse/AMQ-4181?page=com.atlassian.jirafisheyeplugin:fisheye-issuepanel

    
> QueueBrowser ignoring MemoryUsage and Causing Heap Space Error
> --------------------------------------------------------------
>
>                 Key: AMQ-4419
>                 URL: https://issues.apache.org/jira/browse/AMQ-4419
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.8.0
>         Environment: All
>            Reporter: John Stall
>              Labels: OutOfMemoryError, QueueBrowser
>
> Use of QueueBrowser without destination memory limits causes AMQ to run out 
> of heap space.  Retrieving QueueBrowser elements appears to ignore global 
> MemoryUsage and default browsePageSize of 200.  Install default 5.8.0 binary 
> distro.  Create 5000 persistent messages in queue and browse to see contents 
> . Shutdown, and change the queue policy entry so that it doesn't limit the 
> destination memory(remove memoryLimit="1mb").  Startup broker, and attempt to 
> view the same 5000 entries.  This time the results will not be limited and 
> the broker will run out of heap space.  Same occurs if using QueueBrowser 
> programmatically.  Works in previous versions as results were limited by page 
> size.
> May be related to-
> https://issues.apache.org/jira/browse/AMQ-4181?page=com.atlassian.jirafisheyeplugin:fisheye-issuepanel

--
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

Reply via email to