Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DA987FF83 for ; Sat, 30 Mar 2013 14:01:16 +0000 (UTC) Received: (qmail 2467 invoked by uid 500); 30 Mar 2013 14:01:16 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 2386 invoked by uid 500); 30 Mar 2013 14:01:16 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 2355 invoked by uid 99); 30 Mar 2013 14:01:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 Mar 2013 14:01:15 +0000 Date: Sat, 30 Mar 2013 14:01:15 +0000 (UTC) From: "John Stall (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMQ-4419) QueueBrowser ignoring MemoryUsage and Causing Heap Space Error MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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 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 was: Use of QueueBrowser with memory limits in policy entry causes AMQ to crash and 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. 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 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 -- 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