Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=dk20050327; d=earthlink.net;
  b=IyxV/XKsZdpr1ljCnRCUVeIEpro/eI+rB+ORbb5JpgfRYf9zu5tjZrf7mGXk7f7C;
  h=Received:Message-ID:Date:From:User-Agent:X-Accept-Language:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Message-ID: <43036FB3.2030704@earthlink.net>
Date: Wed, 17 Aug 2005 13:11:15 -0400
From: Dave Colasurdo <davecola@earthlink.net>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version: 1.0
To: user@geronimo.apache.org
Subject: Re: Geronimo disk footprint growth at startup
References: <43034E69.4050705@earthlink.net>
 <7b3355cb050817082634afffa1@mail.gmail.com>
In-Reply-To: <7b3355cb050817082634afffa1@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Thanks Bruce.. A few followup questions..

Is there any bound on how large these files can grow or a way to 
configure a smaller value for the recovery log?

Why does a simple server startup require 41M of recovery data?  No user 
applications have been installed on this server yet.

Just wondering if there is a way to limit the default disk footprint 
requirement for geronimo..


Bruce Snyder wrote:
> On 8/17/05, Dave Colasurdo <davecola@earthlink.net> wrote:
> 
> 
>>I've recently noticed that the geronimo disk footprint (on a Windows
>>platform) seems to grow from 55M to 96M when the application server is
>>started.  It seems that the culprit is
>>\geronimo\var\activemq\journal\log-00*.dat..
>>
>>What exactly are these log files?  Is there a simple way to disable this
>>behavior?  Should this be disabled by default in the Geronimo v1
>>distributions?
> 
> 
> That's the journaling log file produced by the High-speed ObjectWeb
> Logger (HOWL) (http://howl.objectweb.org/) that is used by the
> Geronimo transaction manager. This log file facilitates transaction
> recovery within the server in the event of a server crash and is often
> known as a recovery log. As for disabling the use of this file, I
> suppose that a property and a null journal class of some sort could be
> implemented, but I wouldn't recommend this.
> 
> Bruce