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 B160E1074E for ; Wed, 26 Mar 2014 14:06:33 +0000 (UTC) Received: (qmail 85836 invoked by uid 500); 26 Mar 2014 14:06:33 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 85357 invoked by uid 500); 26 Mar 2014 14:06:28 -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 85058 invoked by uid 99); 26 Mar 2014 14:06:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Mar 2014 14:06:22 +0000 Date: Wed, 26 Mar 2014 14:06:22 +0000 (UTC) From: "Gary Tully (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AMQ-4971) OOM in DemandForwardingBridge 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-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-4971. ----------------------------- Resolution: Not A Problem > OOM in DemandForwardingBridge > ----------------------------- > > Key: AMQ-4971 > URL: https://issues.apache.org/jira/browse/AMQ-4971 > Project: ActiveMQ > Issue Type: Bug > Components: Broker > Affects Versions: 5.9.0 > Reporter: Yuriy Sidelnikov > Labels: features > Attachments: AMQ-4971.patch > > > DemandForwardingBridge sends messages to the other broker and asynchronously waits for ACKs keeping message bodies in heap. Amount of un-ACK-ed messages kept in heap is not limited. If local producer is fast then whole heap will be consumed by messages waiting to be ACK-ed by other broker. > Possible option to fix the issue: > Don't wait for ACK from other broker when forwarding the message if some threshold of un-ACK-ed messages is reached. -- This message was sent by Atlassian JIRA (v6.2#6252)