Return-Path: 
 <users-return-37010-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-users-archive@www.apache.org
Delivered-To: apmail-activemq-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 77FE910092
	for <apmail-activemq-users-archive@www.apache.org>;
 Thu, 21 Nov 2013 23:13:42 +0000 (UTC)
Received: (qmail 12142 invoked by uid 500); 21 Nov 2013 23:13:42 -0000
Delivered-To: apmail-activemq-users-archive@activemq.apache.org
Received: (qmail 12024 invoked by uid 500); 21 Nov 2013 23:13:41 -0000
Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@activemq.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@activemq.apache.org>
List-Post: <mailto:users@activemq.apache.org>
List-Id: <users.activemq.apache.org>
Reply-To: users@activemq.apache.org
Delivered-To: mailing list users@activemq.apache.org
Received: (qmail 12016 invoked by uid 99); 21 Nov 2013 23:13:41 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Nov 2013 23:13:41 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of christian.posta@gmail.com
 designates 209.85.217.181 as permitted sender)
Received: from [209.85.217.181] (HELO mail-lb0-f181.google.com)
 (209.85.217.181)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Nov 2013 23:13:36 +0000
Received: by mail-lb0-f181.google.com with SMTP id q8so351598lbi.12
        for <users@activemq.apache.org>; Thu, 21 Nov 2013 15:13:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=Nsb0VYp7elm0F1V0eoFBFSR+cLqQ/TXTnJ4/jGIHne4=;
        b=Ga6lWmVstyPJRwGEipE6hBh4ohYpv7hnybU2NLbnssLRU5500hUt0HHj0VnJX6GbDq
         UhqlsOb70my/nrhI/SmGE9MMpDn7VfnUn2kfaJ0fJU4D0ktu4a8oK2i7woY9mnYmQdSw
         KWxi10toe6ExT/42PdCiQQAFMRqOQYlr3kYKKGktbY9dV97haGbRygU7yQiU56qC+B+v
         X2kThjuY2M2FbXG9hFLkG7dBC496Xnrlq3+Osk3ED62358ooh7JYvcd9pYHGK2Em6S3W
         FTC5THY18W0hdWrXqLHqJ0ejltE8o/aOpPGKrRhsFZPMbz/30KFCRm08W77Crp7JUlvj
         Twzg==
MIME-Version: 1.0
X-Received: by 10.112.171.228 with SMTP id ax4mr6539451lbc.6.1385075595759;
 Thu, 21 Nov 2013 15:13:15 -0800 (PST)
Received: by 10.114.243.139 with HTTP; Thu, 21 Nov 2013 15:13:15 -0800 (PST)
In-Reply-To: 
 <443BCE38E921434394B45FF0813FA578053E8A34@MSGEXSV21106.ent.wfb.bank.corp>
References: 
 <443BCE38E921434394B45FF0813FA578053E8A34@MSGEXSV21106.ent.wfb.bank.corp>
Date: Thu, 21 Nov 2013 16:13:15 -0700
Message-ID: 
 <CAKS7T5N+9PQYKR+Kh37KfjqWzwhaDe2Fwuo582vURsvZqnLbQA@mail.gmail.com>
Subject: Re: Producer Flow Block - Consumer Deadlock after max memory limits
 exceeded
From: Christian Posta <christian.posta@gmail.com>
To: "users@activemq.apache.org" <users@activemq.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org

Inline...

On Thu, Nov 21, 2013 at 10:51 AM,  <barry.barnett@wellsfargo.com> wrote:
> Version: Active MQ v5.8
> Embedded Broker, Producer, Consumer all within same JVM
>
> If max memory limits are set to 320MB, which equates to 10 journal files (32MB per file), the files cannot be cleared even if there is 1 message on the DLQ.

So you might need to post your config (or show the code for your
config if embedded). "Memory Limits" set to 320MB isn't the same thing
as "Store Limits" set to 320MB with 32MB journal files. Individual
files will be cleared out if there are no useful artifacts in them
(messages, durable subscription info, producer audit data structures,
etc...). The default cleanup period is 30s:

eg:

<kahaDB cleanupInterval="30000" ..>



>This 1 message blocks the freeing up of the journal file where it resides.  In order to resolve this, the JVM is >recycled.  I'm sure there is a better way of resolving this issue.  Any advice?

Are producer/consumer using same connection? What ack mode is your
consumer using?

Since this is embedded (broker,producer,consumer) it should be easy
enough to extract out the salient points and put together a unit test.
If you provide something concrete like that, I can take a look and
tell you exactly what's happening.


>
> Regards,
>
> Barry Barnett
> WMQ Enterprise Services & Solutions
> Wells Fargo
> Cell: 704-564-5501
>
>
>



-- 
Christian Posta
http://www.christianposta.com/blog
twitter: @christianposta