[Anthill-pro] Build server running out of memory

[Yanko, Curtis]

What is the relationship with All Build Lives? Do I set it to the max
value in Days and the Sum or Youngest? 


===
-Curt
W: 860.702.9059
M: 860.881.2050

-----Original Message-----
From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Eric
Minick
Sent: Thursday, February 14, 2008 10:54 AM
To: AnthillPro user and support list.
Subject: Re: [Anthill-pro] Build server running out of memory

Ken,

I know earlier this week our guys found a few memory leaks and patched
those up. Those might be contributing to these out of memory errors that
you're hitting. As for the cleanup policies, you do need to set both a
number and time.

To be cleaned up, an item has to be outside of both the time and number
specified. So if you have a policy that keeps the last 10 successful
builds and the last week worth of builds it would play out like this: If
you built the project once a day, you would have 10 days worth of builds
since you are keeping the last ten. If you built the project once an
hour, you would have dozens of builds since you would have the whole
week's worth.

-- Eric

Pacileo, Kenneth wrote:
>
> All,
>
>  
>
> Our build server just ran out of memory again. This happened a couple 
> weeks ago when we were running multiple cleanup jobs at the same time.
> We increased the memory to 512MB and changed the way we run the 
> cleanup jobs. This morning, none of the cleanup jobs were running.
> Only builds were being run but the build server still ran out of 
> memory. Below is a portion of the stack trace. Any ideas what can be 
> causing this and where we can look?
>
>  
>
> Also, our ./server/var/log directory has 49670 objects in it. Some of 
> the directories date back three months. Our clean up policies are set 
> to keep only a couple of the last builds but we do not limit the 
> timeframe. Do both values need to be set? What is the recommended 
> process for setting up cleanup policies?
>
>  
>
>  
>
> resolved 1.0.0.${+property:BuildNum} to 1.0.0.53
>
> java.lang.OutOfMemoryError
>
> java.lang.OutOfMemoryError
>
> java.lang.OutOfMemoryError
>
> java.lang.OutOfMemoryError
>
> java.lang.OutOfMemoryError
>
> java.lang.OutOfMemoryError
>
> java.lang.OutOfMemoryError
>
> java.lang.OutOfMemoryError
>
> java.lang.OutOfMemoryError
>
> java.lang.OutOfMemoryError
>
> java.lang.OutOfMemoryError
>
> java.lang.OutOfMemoryError
>
> java.lang.OutOfMemoryError
>
> com.urbancode.anthill3.domain.persistent.PersistenceRuntimeException: 
> java.lang.OutOfMemoryError
>
>         at
> com.urbancode.anthill3.domain.persistent.Handle.dereference(Handle.jav
> a:162)
>
>         at
> com.urbancode.anthill3.domain.jobtrace.JobTrace.getBuildProfile(JobTra
> ce.java:127)
>
>         at
> com.urbancode.anthill3.domain.jobtrace.vanilla.VanillaJobTrace.getProj
> ect(VanillaJobTrace.java:52)
>
>         at
> com.urbancode.anthill3.domain.jobtrace.vanilla.VanillaJobTraceDaoSql.i
> nsert(VanillaJobTraceDaoSql.java:123)
>
>         at
> com.urbancode.anthill3.persistence.UnitOfWorkDefault.commit0(UnitOfWor
> kDefault.java:136)
>
>         at
> com.urbancode.anthill3.persistence.UnitOfWork.commit(UnitOfWork.java:7
> 00)
>
>         at 
> com.urbancode.anthill3.services.jobs.Job.<init>(Job.java:64)
>
>         at
> com.urbancode.anthill3.services.jobs.JobServiceDefault.run(JobServiceD
> efault.java:267)
>
>         at
> com.urbancode.anthill3.services.notification.NotificationService.handl
> eWorkflowEndEvent(NotificationService.java:182)
>
>         at
> com.urbancode.anthill3.services.notification.NotificationService.acces
> s$100(NotificationService.java:34)
>
>         at
> com.urbancode.anthill3.services.notification.NotificationService$Workf
> lowEndEventListener.handleEvent(NotificationService.java:85)
>
>         at
> com.urbancode.anthill3.services.event.EventService$EventHandleRunnable
> .run(EventService.java:72)
>
>         at
> com.urbancode.commons.util.ThreadPool$WorkerThread.run(ThreadPool.java
> :208)
>
> Caused by: java.lang.OutOfMemoryError
>
>  
>
> Regards,
>
> Ken Pacileo
>
> UnitedHealth Group IT
>
>  
>
>  
>
>
>
> This e-mail, including attachments, may include confidential and/or 
> proprietary information, and may be used only by the person or entity 
> to which it is addressed. If the reader of this e-mail is not the 
> intended recipient or his or her authorized agent, the reader is 
> hereby notified that any dissemination, distribution or copying of 
> this e-mail is prohibited. If you have received this e-mail in error, 
> please notify the sender by replying to this message and delete this
e-mail immediately.
> ----------------------------------------------------------------------
> --
>
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>   
_______________________________________________
Anthill-pro mailing list
Anthill-pro at lists.urbancode.com
http://lists.urbancode.com/mailman/listinfo/anthill-pro


This e-mail, including attachments, may include confidential and/or 
proprietary information, and may be used only by the person or entity to 
which it is addressed. If the reader of this e-mail is not the intended 
recipient or his or her authorized agent, the reader is hereby notified 
that any dissemination, distribution or copying of this e-mail is 
prohibited. If you have received this e-mail in error, please notify the 
sender by replying to this message and delete this e-mail immediately.