Mailing-List: contact dev-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@continuum.apache.org
Received-SPF: pass (athena.apache.org: domain of muralihere@gmail.com
 designates 64.233.184.231 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=Zxy447OgZxLx+GXU9cKYFcCbPVLtFoxPIL2S1XA1S4anMwHxunpXWxJgaqfwkoYJOxDtCekjHYxUWgep89RQ8L9KrzbH+vbaBaoP4nwgcG3GjB+5rWdMP4jsLVy7wWMVx/aOLur50WDKb2TqMn+aa+BBmLqtr44cZVSBU4HzRCo=
Message-ID: <7cfb44750803210635i3f698d3av7af2c5214212de9@mail.gmail.com>
Date: Fri, 21 Mar 2008 13:35:20 +0000
From: "murali mohan" <muralihere@gmail.com>
To: dev@continuum.apache.org
Subject: Re: OutOfMemory Error because of large build (log) files
In-Reply-To: <f345f3480803210352q398aa4fdm6157920438956a8c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_1003_18093546.1206106520083"
References: <7cfb44750803201314x14caf29bq91e4426a1cc14a37@mail.gmail.com>
	 <f345f3480803210352q398aa4fdm6157920438956a8c@mail.gmail.com>

------=_Part_1003_18093546.1206106520083
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Fri, Mar 21, 2008 at 10:52 AM, Emmanuel Venisse <
emmanuel.venisse@gmail.com> wrote:

> On Thu, Mar 20, 2008 at 9:14 PM, murali mohan <muralihere@gmail.com>
> wrote:
>
> > I have been facing this error because of large build output files
> created
> > by
> > builds in my projects. The logs have a threshold of INFO and they do
> > create
> > large files even then because of the sheer size of the project.
> >
> > This causes OutOfMemory errosr in two places:
> > 1) The webapp - When we click on the build results page (And if the
> build
> > output file is huge)
> > 2) The Reports Generation phase (Usually towards the end of the build) -
> > This is a major problem. Because the build does not complete even though
> > it
> > has run all the phases till Test. And the result is that we dont have
> the
> > surefire reports link in the build result page and also there is no
> > notification email sent out.
> >
> > For now, in my project, i have just put in a check for the size of the
> > file
> > and if it is larger than 50MB, i just put in a messsage that the file is
> > Huge. This may not be an ideal patch for this problem. So the questions
> i
> > have are:
>
>
> Yes, it isn't an ideal patch.
>
>
> > 1) Can't we avoid reading the files into a String during report
> > generation?
>
>
> You can try to set the include* parameter in application.xml for the
> MailContinuumNotifier component;
>
>
> > 2) In the build results page, we can have a save file button instead of
> > opening the whole file in memory?
>
>
> It would be good, can you write a patch?


I will try. Will update later this week.

>
>
> >
> > 3) Is there any way we can continue the reports generation of a failed
> > Build? I am pretty sure it is not possible today. But , maybe in the
> > future,
> > we can have some flexibility that, even though the Build failed in say
> > phase
> > 3 after successful completion phase 1 and 2, we should be able to
> continue
> > from phase 3. This will be very useful and we can have the full builds
> > even
> > though it didnt run correctly during the scheduled time.
>
>
> hmm, I'm not sure to undrstand what you want to do.


>
> Any suggestions? What do people think of my patch? Should I submit it?
> >
> > Murali.
> >
>

------=_Part_1003_18093546.1206106520083--