Mailing-List: contact issues-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@continuum.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Date: Tue, 11 Jun 2013 23:55:03 -0500 (CDT)
From: "Brent N Atkinson (JIRA)" <jira@codehaus.org>
To: issues@continuum.apache.org
Message-ID: 
 <JIRA.83242.1236674437074.2904.1371012903266@codehaus01.managed.contegix.com>
In-Reply-To: <JIRA.83242.1236674437074@codehaus01.managed.contegix.com>
References: <JIRA.83242.1236674437074@codehaus01.managed.contegix.com>
Subject: [jira] (CONTINUUM-2119) Cleaning up large working directories fails
 with OutOfMemoryError
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


    [ https://jira.codehaus.org/browse/CONTINUUM-2119?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D32659=
9#comment-326599 ]=20

Brent N Atkinson commented on CONTINUUM-2119:
---------------------------------------------

Brett, your comment:=20

{quote}
need to be able to upgrade plexus-utils first
{quote}

Why do you say that upgrading plexus-utils necessary?
               =20
> Cleaning up large working directories fails with OutOfMemoryError=20
> ------------------------------------------------------------------
>
>                 Key: CONTINUUM-2119
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2119
>             Project: Continuum
>          Issue Type: Bug
>          Components: Core system
>    Affects Versions: 1.2.3
>            Reporter: Frank F=F6rstemann
>            Assignee: Brent N Atkinson
>             Fix For: 1.4.2
>
>         Attachments: CONTINUUM-2119-continuum-core.patch
>
>
> The action clean-working-directory runs out of heap space while cleaning =
up huge working directories (30GB / 500.000 files & directories in our case=
):
> 2009-03-08 06:00:14,582 [pool-1-thread-1] INFO  buildController  - Initia=
lizing build
> 2009-03-08 06:00:15,286 [pool-1-thread-1] INFO  buildController  - Starti=
ng build of ivu_plan_nightly_build
> 2009-03-08 06:00:15,301 [pool-1-thread-1] INFO  buildController  - Purgin=
g exiting working copy
> 2009-03-08 06:00:15,301 [pool-1-thread-1] INFO  buildController  - Perfor=
ming action clean-working-directory
> 2009-03-08 06:31:39,209 [Thread-3] ERROR taskQueueExecutor#build-project =
 - Error executing task
> edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: java.l=
ang.OutOfMemoryError: Java heap space
> =09at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult=
(FutureTask.java:301)
> =09at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(Futur=
eTask.java:120)
> =09at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$E=
xecutorRunnable.waitForTask(ThreadedTaskQueueExecutor.java:159)
> =09at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$E=
xecutorRunnable.run(ThreadedTaskQueueExecutor.java:127)
> Caused by: java.lang.OutOfMemoryError: Java heap space
>  The issue seems to be caused by the implementation in CleanWorkingDirect=
oryAction: the FileSetManager used to delete the working directory first sc=
ans all files & directores to create an object representation of the tree a=
nd then deletes the tree by scanning through the objects. As no filter cond=
ition is required using org.codehaus.plexus.util.FileUtils to directly dele=
te the tree would avoid these kind of problems.
> I'll attach a patch based on 1.2.3.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira