cruise control throws out of memory exception if the log file size is huge

We use cruise control for our regular build and testing setups. The tests are
continuously run and if something fails a mail is sent to the subscriber
list about the failure.

We have a test which produces a huge amount of log (around 60MB) which is
finally written to disk. But in this case cruise control throws an out of
memory exception and then fails to send any mail about the failure.

Since log files are written on disk and we get OOME then its clear that logs
are first written in the memory and then finally flushed to disk. Is there
any setting by which we can stop this from happening. I mean by increasing
the heap space for log files or getting it to flush to disk more frequently. 

Any pointer to solve this would be highly helpful.

Thanks
Raghvendra Singh
-- 
View this message in context: http://www.nabble.com/cruise-control-throws-out-of-memory-exception-if-the-log-file-size-is-huge-tp22718880p22718880.html
Sent from the CruiseControl - User mailing list archive at Nabble.com.


------------------------------------------------------------------------------