[Anthill-pro] OutOfMemory exception
Steve Boone
sbb at urbancode.com
Mon Sep 10 08:28:04 CDT 2007
Uldis,
If you are running out of space on an agent there is most likely two
causes. If you are using a different working directory for every project
you are building, this practice can take up a good portion of space,
especially if you are building a large number of projects. The second cause
could be your codestation cache has grown out of control.
If you are using a different working directory for each project, you will
need to create a cleanup step, and have it run after your build completes.
This will ensure that the files created are removed.
If this is not the case, and you are using cleanup steps within your
projects, then odds are your codestation cache has grown rather large.
Check your ~/.codestation/cache directory to see if that is what is
consuming the majority of your space. If it is, you can delete the files
from there, and to prevent this from happening in the future you can turn
the agent caching off.
To do this, edit the codestation.properties file located in
~/.codestation/ If the file does not exist, go ahead and create it. Add
the following line to the file.
codstation.noCache=true
As for the Cleanup Policies, anytime they run, they will create a Misc. Job
that you will see on the dashboard (much like an email notification, or
other Misc Job) if you are not seeing any Misc Jobs for cleanup, then they
most likely are not running. You do not need to set both the "Days" and
"Count" fields, the Days field can be left empty if you choose to keep the
buildlife indefinitely.
Cleanup Policies only clean the server, it will clean up logs when
corresponding job traces are deleted, but it does not delete working
directories for jobs. If this is the functionality you are looking for, I
would suggest adding a cleanup step to your individual jobs as you find
necessary. You could also create a cleanup workflow, and set it to a
trigger and have it cleanup only when you felt it was appropriate.
Regards,
Steve Boone
On 9/10/07, Uldis Karlovs-Karlovskis <uldisk at ctco.lv> wrote:
>
> Hello, this is a second time when my anthill server performance is
> descended and on this time I see that there are OutOfMemory exceptions in
> AntHill server log. I have server with 4GB ram so this can`t be an issue. As
> I understand I can raise an JVM max memory in JAVA_OPTs. But how long this
> will help if my server uptime is only 10 days? In this moment the anthill
> server process is taking 518M of memory.
>
>
>
> *Uldis Karlovs - Karlovskis*
>
> *Build System and Deployment Administrator*
>
> *System Configuration Management*
>
> *C.T.Co*
>
> *Mobile**: +371 29 345 210*
>
>
>
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20070910/31a947e6/attachment-0001.htm
More information about the Anthill-pro
mailing list