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 52CB01103A for ; Fri, 16 May 2014 13:58:45 +0000 (UTC) Received: (qmail 62694 invoked by uid 500); 16 May 2014 11:19:01 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 10060 invoked by uid 500); 16 May 2014 11:01:59 -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 88705 invoked by uid 99); 16 May 2014 10:54:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 May 2014 10:54:22 +0000 Date: Fri, 16 May 2014 10:54:22 +0000 (UTC) From: "Michael Samson (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMQ-5188) AMQ broker throws OutOfMemoryError even when global flow-control memoryUsage limit is imposed 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-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Samson updated AMQ-5188: -------------------------------- Description: * 5.8.0 broker was configured with persistence=false and a global * 5.8.0 broker JVM memory was set to default of 1G * No active consumers * 10 Qpid (version .26) AMQP producers sent messages to 10 broker queues until flow control was reached * Over time the AMQP connections/producers were closed and recreated and they reattempted to send messages. As this cycle continues, eventually ActiveMQ threw OutOfMemoryErrors. I grabbed a heap dump and ActiveMQTextMessages consumed 874M of the heap. Taking a closer look, it appears that each org.apache.activemq.broker.region.Queue's messagesWaitingForSpace map grows unbounded and causes the OutOfMemory. I will attach a sample maven program that reproduces the problem along with my activemq configuration, heap screenshots, etc. Are their any workarounds to this issue? It is a potential use case for our customers if their queue consumers die for an extended period of time. was: * 5.8.0 broker was configured with persistence=false and a global * 5.8.0 broker JVM memory was set to default of 1G * No active consumers * 10 Qpid (version .26) AMQP producers sent messages to 10 broker queues until flow control was reached * Over time the AMQP connections/producers were closed and recreated and they reattempted to send messages. As this cycle continues, eventually ActiveMQ threw OutOfMemoryErrors. I grabbed a heap dump and ActiveMQTextMessages consumed 874M of the heap. Taking a closer look, it appears that each org.apache.activemq.broker.region.Queue's messagesWaitingForSpace map grows unbounded and causes the OutOfMemory. I will attach a sample maven program that reproduces the problem along with my activemq configuration, heap screenshots, etc. Are their any workarounds to this issue? It is a potential use case for our customers if their queue consumers die for an extended period of time. > AMQ broker throws OutOfMemoryError even when global flow-control memoryUsage limit is imposed > --------------------------------------------------------------------------------------------- > > Key: AMQ-5188 > URL: https://issues.apache.org/jira/browse/AMQ-5188 > Project: ActiveMQ > Issue Type: Bug > Components: Broker > Affects Versions: 5.8.0 > Environment: AMQ 5.8.0 broker running on 64-bit Linux > AMQP Qpid (.26) JMS producers running on 64-bin Linux > Reporter: Michael Samson > Attachments: AMQ_heap1.png, AMQ_heap2.png, QpidProducerAMQOutOfMemory.java, activemq.xml, qpid-producer.tar > > > * 5.8.0 broker was configured with persistence=false and a global > * 5.8.0 broker JVM memory was set to default of 1G > * No active consumers > * 10 Qpid (version .26) AMQP producers sent messages to 10 broker queues until flow control was reached > * Over time the AMQP connections/producers were closed and recreated and they reattempted to send messages. As this cycle continues, eventually ActiveMQ threw OutOfMemoryErrors. > I grabbed a heap dump and ActiveMQTextMessages consumed 874M of the heap. Taking a closer look, it appears that each org.apache.activemq.broker.region.Queue's messagesWaitingForSpace map grows unbounded and causes the OutOfMemory. > I will attach a sample maven program that reproduces the problem along with my activemq configuration, heap screenshots, etc. > Are their any workarounds to this issue? It is a potential use case for our customers if their queue consumers die for an extended period of time. > -- This message was sent by Atlassian JIRA (v6.2#6252)