MainServer1's own middleware logs are growing large enough to repeatedly fill server disk space every couple of days, requiring manual cleanup of old log files. How can this log growth actually be controlled at the source?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

First check the actual log content for genuine recurring errors before assuming it's simply excessive normal logging — persistent errors filling the logs might need their own separate investigation. If the logs are otherwise clean, configure proper log rotation and an appropriate log level through the Middleware Server Admin Console, under Main Cluster > Managed Servers > MWS Logging: set a 'Limit Number of Retained Files' value to cap how many historical log files are allowed to accumulate, and set the log level to an appropriately conservative level, commonly Warning, rather than a more verbose default. This addresses the log growth at its source, rather than continuing to rely on manual periodic cleanup of old log files.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions