continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Voigt" <tvo_spam...@gmx.de>
Subject java.lang.OutOfMemoryError
Date Fri, 06 Feb 2009 09:19:13 GMT
Hi,

we keep getting out of memory errors in our nightly builds. The errors seem to happen in the
startup phase, because once maven starts it will run through.

Continuum 1.2.2 runs in a Tomcat. Increasing memory in JAVA_OPTS and MAVEN_OPTS did not fix
the problem, the current settings are -Xmx1400m  -XX:MaxPermSize=512m.

The problem is probably due to the large size the source code, we check out several gigabytes
in a clean checkout and have roughtly 1000 projects. Out of memory problems happened to us
before with other CI applications (Cruisecontrol and Hudson), in CC we got rid of them by
 using CC simply as a cron substitute - but that's not exactly how one should use a CI server.


Any ideas? Here is the output from the log.

2009-02-06 09:46:34,491 [pool-1-thread-1] INFO  buildController  - Initializing build
2009-02-06 09:51:22,277 [pool-1-thread-1] INFO  buildController  - Starting build of XXX
2009-02-06 09:51:22,324 [pool-1-thread-1] INFO  buildController  - Updating working dir
2009-02-06 09:51:22,324 [pool-1-thread-1] INFO  buildController  - Performing action check-working-directory
2009-02-06 09:51:22,324 [pool-1-thread-1] INFO  buildController  - Performing action update-working-directory-from-scm
2009-02-06 09:51:22,355 [pool-1-thread-1] INFO  action#update-working-directory-from-scm 
- Updating project: XXX', id: '1158' to 'D:\Continuum\working-directory\1158'.
2009-02-06 09:51:22,386 [pool-1-thread-1] INFO  org.apache.continuum.scm.manager.Slf4jScmLogger
 - Executing: cmd.exe /X /C "svn --non-interactive update D:\Continuum\working-directory\1158"
2009-02-06 09:51:22,386 [pool-1-thread-1] INFO  org.apache.continuum.scm.manager.Slf4jScmLogger
 - Working directory: D:\Continuum\working-directory\1158
2009-02-06 09:59:26,180 [pool-1-thread-1] INFO  org.apache.continuum.scm.manager.Slf4jScmLogger
 - Executing: cmd.exe /X /C "svn --non-interactive log -v -r "{2009-02-05 10:43:41 +0000}:{2009-02-06
08:59:26 +0000}" http://xxx/trunk"
2009-02-06 09:59:26,180 [pool-1-thread-1] INFO  org.apache.continuum.scm.manager.Slf4jScmLogger
 - Working directory: D:\Continuum\working-directory\1158
2009-02-06 09:59:26,492 [pool-1-thread-1] INFO  action#update-working-directory-from-scm 
- Updated 65 files.
2009-02-06 09:59:26,508 [pool-1-thread-1] INFO  buildController  - Merging SCM results
2009-02-06 09:59:35,663 [pool-1-thread-1] INFO  buildController  - AlwaysBuild configured,
building
2009-02-06 09:59:35,663 [pool-1-thread-1] INFO  buildController  - Performing action update-project-from-working-directory
2009-02-06 09:59:35,663 [pool-1-thread-1] INFO  action#update-project-from-working-directory
 - Updating project 'XXX' from checkout.
2009-02-06 10:00:00,458 [continuumScheduler_Worker-0] INFO  schedulesActivator  - >>>>>>>>>>>>>>>>>>>>>
Executing build job (DEFAULT_SCHEDULE)...
2009-02-06 10:02:15,609 [Thread-3] ERROR taskQueueExecutor#build-project  - Error executing
task
edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError:
Java heap space
	at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:301)
	at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:120)
	at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.waitForTask(ThreadedTaskQueueExecutor.java:159)
	at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:127)
Caused by: java.lang.OutOfMemoryError: Java heap space


Regards, Thomas


-- 
Jetzt 1 Monat kostenlos! GMX FreeDSL - Telefonanschluss + DSL 
für nur 17,95 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a

Mime
View raw message