Return-Path: X-Original-To: apmail-activemq-issues-archive@minotaur.apache.org Delivered-To: apmail-activemq-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 02394186AB for ; Tue, 23 Feb 2016 19:19:17 +0000 (UTC) Received: (qmail 72294 invoked by uid 500); 23 Feb 2016 19:18:18 -0000 Delivered-To: apmail-activemq-issues-archive@activemq.apache.org Received: (qmail 72258 invoked by uid 500); 23 Feb 2016 19:18:18 -0000 Mailing-List: contact issues-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 issues@activemq.apache.org Received: (qmail 72216 invoked by uid 99); 23 Feb 2016 19:18:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Feb 2016 19:18:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 2D2102C14F8 for ; Tue, 23 Feb 2016 19:18:18 +0000 (UTC) Date: Tue, 23 Feb 2016 19:18:18 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: issues@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ARTEMIS-350) possible OOM in replication manager 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/ARTEMIS-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159468#comment-15159468 ] ASF subversion and git services commented on ARTEMIS-350: --------------------------------------------------------- Commit 2fcd474bb3ea83c696e2794cd7b5951494a2b20a in activemq-artemis's branch refs/heads/master from [~jbertram] [ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=2fcd474 ] ARTEMIS-350 fix for potential race It's possible for the latch used for flow control here to get out of sync. In other words, multiple count-downs can occur between count-ups so that the latch always has a count > 0. When this situation arises then every single packet sent to the replica is delayed by 5 seconds. The solution here essentially is to eliminate the latch completely and use a condition/wait/notify pattern. > possible OOM in replication manager > ----------------------------------- > > Key: ARTEMIS-350 > URL: https://issues.apache.org/jira/browse/ARTEMIS-350 > Project: ActiveMQ Artemis > Issue Type: Bug > Reporter: Andy Taylor > Assignee: Andy Taylor > Fix For: 1.3.0 > > > This is becausee we have no flow control, we need to throttle back when the channel is not writable -- This message was sent by Atlassian JIRA (v6.3.4#6332)