Return-Path: 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 B7315D119 for ; Wed, 3 Oct 2012 09:37:16 +0000 (UTC) Received: (qmail 25359 invoked by uid 500); 3 Oct 2012 09:37:16 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 24912 invoked by uid 500); 3 Oct 2012 09:37:10 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 24759 invoked by uid 99); 3 Oct 2012 09:37:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Oct 2012 09:37:08 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gary.tully@gmail.com designates 209.85.215.43 as permitted sender) Received: from [209.85.215.43] (HELO mail-la0-f43.google.com) (209.85.215.43) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Oct 2012 09:37:02 +0000 Received: by lahi5 with SMTP id i5so2883314lah.2 for ; Wed, 03 Oct 2012 02:36:42 -0700 (PDT) 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=kG3vkKGK52tuDRyIHjJR5LcM7Hb1B/5EjLdM3JNJ3lM=; b=xJU6PargaO2BexsZFuxRu8QM2mK/6PG4zSzYmjMUvtYsTf+AfkpvN+u6h2l4BS0NTw rW7BpI4vlOgEq4WuTdfzxSArSsxq1wTyscyTnCyWD5Lz6zigTj3HqyUkkiC3YOeM7ENe nLdXId4G76yWsz8C6UeYWKtb9bEcdGvYxtosov0JJegnlYsGuZUS+YucS0mMy3ql4EU3 HgQ+qKXWR0/oqjzIx15m5XXIJfxXhDnKTuuApNChQxLBXFiwjreYppUQFBpfGunBfZo9 TeTbG9wX2KCMpMpmQS1nnPivx13zDYoAiSo3815FhNB/emhlSqV3aCXZNeqV846CGezI wa+g== MIME-Version: 1.0 Received: by 10.112.87.162 with SMTP id az2mr1532369lbb.42.1349257001946; Wed, 03 Oct 2012 02:36:41 -0700 (PDT) Received: by 10.114.12.38 with HTTP; Wed, 3 Oct 2012 02:36:41 -0700 (PDT) In-Reply-To: <1349214131566-4657414.post@n4.nabble.com> References: <1349209195874-4657406.post@n4.nabble.com> <1349214131566-4657414.post@n4.nabble.com> Date: Wed, 3 Oct 2012 10:36:41 +0100 Message-ID: Subject: Re: what to do when storage is full? From: Gary Tully To: users@activemq.apache.org Content-Type: text/plain; charset=ISO-8859-1 yes it will. if you add a store limit, then eventually an add will block, so a producer will block. you wou't be able to send any more messages until sufficient messages are consumed such that a data file can be released. On 2 October 2012 22:42, Lin Wen Tong wrote: > I moved the kahaDB path to a bigger space and it recovered: > > 2012-10-02 14:16:07,103 [main ] INFO MessageDatabase > - @2056:22703857, 100000 entries recovered .. > 2012-10-02 14:16:17,142 [main ] INFO MessageDatabase > - @2061:27448275, 200000 entries recovered .. > 2012-10-02 14:16:26,910 [main ] INFO MessageDatabase > - @2067:13176930, 300000 entries recovered .. > 2012-10-02 14:16:36,057 [main ] INFO MessageDatabase > - @2073:11643615, 400000 entries recovered .. > 2012-10-02 14:16:49,398 [main ] INFO MessageDatabase > - @2079:22796289, 500000 entries recovered .. > 2012-10-02 14:17:04,877 [main ] INFO MessageDatabase > - @2086:700591, 600000 entries recovered .. > > > I was wondering if adding a limit storage would help: > > > > > > > > > > > -- > View this message in context: http://activemq.2283324.n4.nabble.com/what-to-do-when-storage-is-full-tp4657406p4657414.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com