Comment 5 for bug 453456

the java (cloud, walrus, sc) components' logging uses log4j. the defaults can be found in source under:

clc/modules/core/src/main/resources/log4j.xml

where you'll find the following, which control the file size and the max number of files of this size that can exist

       <param name="MaxFileSize" value="10MB"/>
       <param name="MaxBackupIndex" value="10"/>

for the C components (cc, nc), the logfiles are controlled inside the logprintfl() function, where you'll find logic for handling the roll-over. by default, there can be six files (ex: cc.log, cc.log{0-5}), each of which at most 32MB.

the axis2c.log is rolled once by axis2c itself (axis2c.log and axis2c.log.old), and its size can be set through httpd.conf (128MB by default)

Axis2MaxLogFileSize 128

the httpd-{cc,nc}-error_log (set in httpd.conf, again) is not rolled, but tends to grow very slowly.

finally, i'm not sure where the jetty log rolling policy is set, but will find out and comment here.