Stability and Performance - Oracle WebLogic Server 12c Advanced Administration - page 214

6. Type :ws! to save the file and exit.
7. Change the file permissions:
[root@prod01]# chmod 755 /etc/cron.hourly/wls-stdout-logrotate
8. Repeat the previous steps for all machines in the PROD_DOMAIN .
How it works...
The logrotate settings will be read from the wls-stdout-logrotate.conf
configuration file. The file was saved in the root directory of the WebLogic domain,
but it can be saved anywhere.
A crontab job was added to run hourly in the form of a script. This configuration must be
executed by the root user.
When the crontab job runs, it checks for all .out files that matches the path
$OMAIN_HOME/servers/PROD_*/logs/*.out . If the file size is over 50 MB, the job
will copy the file content to a new one ( PROD_Server01.out.1 ) and then truncate the
original file.
The copytruncate parameter guarantees that the rotation works properly since WebLogic
keeps the stream to the .out file open.
When the STDOUT logfile reaches the file size limit of 2 GB in 32-bit
environments, the WebLogic Server instance can hang. Rotating the
STDOUT can prevent this situation from happening.
See also
F Limiting the logging disk usage
F Turning off the domain logging
Turning off domain logging
The WebLogic Domain's log concentrates all the WebLogic Managed Server loggings in one
single log managed by the Administration Server.
The domain log can become a bottleneck and affect the performance in certain scenarios
with a very large domain with several Managed Servers.
In this recipe, the log will be turned off for the PROD_DOMAIN domain.