From dev-return-6784-apmail-continuum-dev-archive=continuum.apache.org@continuum.apache.org Thu Mar 20 20:15:12 2008 Return-Path: Delivered-To: apmail-continuum-dev-archive@www.apache.org Received: (qmail 22920 invoked from network); 20 Mar 2008 20:15:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Mar 2008 20:15:12 -0000 Received: (qmail 50738 invoked by uid 500); 20 Mar 2008 20:15:10 -0000 Delivered-To: apmail-continuum-dev-archive@continuum.apache.org Received: (qmail 50713 invoked by uid 500); 20 Mar 2008 20:15:09 -0000 Mailing-List: contact dev-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@continuum.apache.org Delivered-To: mailing list dev@continuum.apache.org Received: (qmail 50703 invoked by uid 99); 20 Mar 2008 20:15:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Mar 2008 13:15:09 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of muralihere@gmail.com designates 64.233.184.224 as permitted sender) Received: from [64.233.184.224] (HELO wr-out-0506.google.com) (64.233.184.224) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Mar 2008 20:14:31 +0000 Received: by wr-out-0506.google.com with SMTP id 69so1083691wri.5 for ; Thu, 20 Mar 2008 13:14:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=81en86z4qPEq6KYnqRw25eXCHilnlQj0o2a9RJO2j/4=; b=QeZtpGI9S5kg60oz/ddR+YlbPDIAvrHO2qBtt8Mvd0XfKKPaLiqZY5dNZkVEDcrhQ4jf0DTl73CKbqfcGDfTemvx79/t+8GMhoFlhVx0BUHKajiOQFGUcbcjK7v+c7A642Yps5bDol91M5/qwMrNRiO2B0if1/Ir15EAnEO6xVk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:mime-version:content-type; b=WZm/zGkQuXDESLvLR181LQeHl+0Q3vehyPqAVEU22GKWKLNSzVVH8eEL5fSCvfSX67pesyoY6PIdohwnkUSLmST3+kV3ZUKuGUa5V5qcET41jVIT60lUDpMyt+GrF4y7IdvH61gi6/n1aIjJbsLykbaF4gH05aJqf1CQcgAQ6F4= Received: by 10.114.13.1 with SMTP id 1mr4454482wam.4.1206044081579; Thu, 20 Mar 2008 13:14:41 -0700 (PDT) Received: by 10.114.148.16 with HTTP; Thu, 20 Mar 2008 13:14:41 -0700 (PDT) Message-ID: <7cfb44750803201314x14caf29bq91e4426a1cc14a37@mail.gmail.com> Date: Thu, 20 Mar 2008 20:14:41 +0000 From: "murali mohan" To: dev@continuum.apache.org Subject: OutOfMemory Error because of large build (log) files MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_39060_8271552.1206044081577" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_39060_8271552.1206044081577 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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: 1) Can't we avoid reading the files into a String during report generation? 2) In the build results page, we can have a save file button instead of opening the whole file in memory? 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. Any suggestions? What do people think of my patch? Should I submit it? Murali. ------=_Part_39060_8271552.1206044081577--