Re: CruiseControl process death issue

Hello Antoine,

No actually I am running Cruisecontrol on a Solaris box (SunOS
5.9/Solaris 9). CruiseControl version: 2.8.2. Where could I see a trace
as I could not find a wrapper.log file?  


Thanks and Regards,
Aditya Kulkarni
P Save the environment. Please don't print this email unless you really
need to.*

-----Original Message-----
From: Antoine Levy Lambert [mailto:[email protected]] 
Sent: Wednesday, March 17, 2010 7:05 PM
To: [email protected]
Subject: Re: [Cruisecontrol-user] CruiseControl process death issue

Hello Aditya,

are you running CruiseControl on Windows ? If yes, look in the
wrapper.log file (usually found under C:\Program
Files\CruiseControl\logs\wrapper.log). If the process dies because it
goes out of memory, you would see a stack trace there. I am using
CruiseControl 2.7.2 I think and it is extremely stable, however I run it
with non default memory options, I think with -Xmx1024m -Xms256m.

Regards,

Antoine

Kulkarni, Aditya (Aditya) wrote:
> Hello,
>  
> We were facing the problem that the Cruisecontrol auto builds (build
> loop) stops working because maybe the Cruisecontrol process dies. 
> Hence, we have to manually force the build or restart Cruisecontrol. 
> Is there any fix to this problem? Would an upgrade to 2.8.3 help in 
> this respect (current is 2.8.3) ? Could someone suggest a solution?
>  
> Thanks,
> Aditya Kulkarni
>  
>  


------------------------------------------------------------------------
------
Download Intel® Parallel Studio Eval Try the new software tools for
yourself. Speed compiling, find bugs proactively, and fine-tune
applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Cruisecontrol-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev